Data processing caught up by 22:45 UTC yesterday evening.
Posted Aug 07, 2025 - 10:34 CEST
Update
The pipeline for this partition of the data is still catching up. At the moment ~15.5M messages are left. Our estimate is that will take about 8 more hours to catchup to real-time.
We will provide a next update tomorrow morning (UTC)
Posted Aug 06, 2025 - 16:36 CEST
Monitoring
The data in the RIPEstat looking glass is delayed for some peers of rrc00. The data inflow overwhelmed the process processing this part ("partition") of the data causing it to slip behind.
We have temporarily de-peered the peer and asked them to reconfigure their session.
At the time of writing, the backlog is around 23M BGP messages. We can't skip data because this would cause the BGP state to be out of sync. This means that we need to process the backlog.
The delay for the affected peers is up to 7 hours. The delay for all other peers is below 75 seconds from the moment a BGP messages arrives at our collector until it is visible in the looking glass.
**Only** the following peers of rrc00 are affected: 31.169.65.90 45.12.55.0 85.132.60.10 93.159.141.1 102.217.156.3 103.142.152.18 103.200.113.1 103.212.68.10 109.248.43.5 178.208.11.4 185.181.60.126 192.248.121.251 194.28.97.2 194.50.19.65 194.50.99.88 213.200.87.254 2001:19f0:5001:1cb5:5400:1ff:fed6:7f3f 2001:678:aa4::5 2001:67c:21ec:5000:5800:ff:fe7e:6ded 2001:7f8:e7:c232::6358 2001:def:c000:100::12 2401:dd00:1:1::218 2402:f740:1000::1 2607:fad8::1:9 2a00:1578:dead::1 2a00:5740:0:4::2 2a03:94e0:ffff:185:181:60:0:126 2a0a:4944:fe::1 2a0b:3b00::4 2a0c:b641:400::1 2c0f:6300:0:ffb::0
Posted Aug 06, 2025 - 12:35 CEST
This incident affected: Non-Critical Services (RIPEstat).