Section Outage History
Section is up right nowPingoru has recorded 50 incidents for Section: 1 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 41 (0%) |
Incidents, newest first
Major February 20, 2026 Connectivity issues with Section Anycast network 5h 5m Anycast
Started Feb 20, 2026, 06:45 PM UTC· resolved Feb 20, 2026, 11:51 PM UTC
- investigating Feb 20, 2026, 06:45 PM UTC
Section is currently experiencing connectivity issues with the Section Anycast network. Engineers are investigating this issue. Updates will continue to be provided on the status of this issue.
- identified Feb 20, 2026, 07:10 PM UTC
We’ve identified an issue with an upstream partner that is affecting the Section Anycast network.
- monitoring Feb 20, 2026, 07:27 PM UTC
We have followed mitigation steps provided by our upstream partner to readvertise affected IP prefixes. We are now seeing traffic levels stabilize and connectivity issues beginning to resolve across the network. We will continue to monitor the situation closely to ensure full stability.
- monitoring Feb 20, 2026, 07:44 PM UTC
We are now seeing connectivity and traffic flow return to normal levels. We will continue to monitor to ensure the stability of these routes.
- monitoring Feb 20, 2026, 07:59 PM UTC
We are continuing to monitor for any further issues.
- monitoring Feb 20, 2026, 09:04 PM UTC
While we await a final resolution from our upstream partner regarding the broader incident, our services are currently operating normally. We will continue to monitor the situation until their investigation is fully concluded.
- resolved Feb 20, 2026, 11:51 PM UTC
The incident has been resolved. Our upstream partner has also officially concluded their investigation and closed the underlying incident. We have verified that all services are operating at expected performance levels and have now concluded our monitoring period. We apologize for the disruption and appreciate your patience while we worked toward this resolution.