Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
The last data (kafka partition) recovered at 04:46. This incident has been resolved.
As a follow-up we will make changes to our alerts for this service.
When a single node fails, the alert only pages during office-hours. A composite alert, based on the count of the single node alert, fires when multiple nodes are failing. This alert inherited labels that also routed it as office-hours only.
The looking-glass is still recovering the data for the final peers. Around 1/10th of the peers on RRC25 are still delayed due to a high volume of messages for this part of the data.
The current estimate is that this will recover around 05:00 UTC. We will update this message tomorrow.
The database system has recovered. In turn this caused the API used by RIPEstat to recover. The RIPEstat API latency is recovering and API throughput is close to normal.
The looking-glass database is now replaying BGP messages from the last hours and will be behind until this recovers.
The database system used for the RIS looking glass ran out of file descriptors due to a low limit in our configuration (32k). This caused an internal API to consume all available processing slots while handling looking glass requests.
We are recovering the database system.
Multiple RIPEstat APIs (looking-glass, ris-peers, many others) are unavailable. We received the first report in a ticket at 0:58 UTC and the issue is ongoing.
We are currently investigating the issue.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with