Historia awarii Section

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.

We’ve identified an issue with an upstream partner that is affecting the Section Anycast network.

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.

We are now seeing connectivity and traffic flow return to normal levels. We will continue to monitor to ensure the stability of these routes.

We are continuing to monitor for any further issues.

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.

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.

Section is currently experiencing issues with our Management Console and API availability. End-users may experience issues with accessing the console or performing certain functions, including degraded performance with API's. Engineers are investigating this issue. Updates will continue to be provided on the status of this issue.

This incident has been resolved.

Section is currently experiencing issues with our Management Console and API availability. End-users may experience issues with accessing the console or performing certain functions, including degraded performance with API's. Engineers are investigating this issue. Updates will continue to be provided on the status of this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Section is currently experiencing issues with our Management Console and API availability. End-users may experience issues with accessing the console or performing certain functions, including degraded performance with API's. Engineers are investigating this issue. Updates will continue to be provided on the status of this issue.

We are continuing to investigate this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Section is currently experiencing issues with our Management Console and API availability. End-users may experience issues with accessing the console or performing certain functions, including degraded performance with API's. Engineers are investigating this issue. Updates will continue to be provided on the status of this issue.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Section is currently experiencing degraded performance with the Section Anycast network. Engineers are investigating this issue. Updates will continue to be provided on the status of this issue.

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

Section is currently tracking an issue in AWS US-East 2 region that is currently impacting multiple customers. See here for more details: https://health.aws.amazon.com/health/status Section has automatically routed customer traffic away from this AWS POP however if customer origins are deployed in this region they will be experiencing 522 and 524 errors. Updates will continue to be provided on the status of this issue.

A fix has been implemented and we are monitoring the results.

AWS has resolved the issue with AWS US-East-2 (Ohio) For more information please reference the AWS health status page here: https://health.aws.amazon.com/health/status

We are currently investigating an issue with several AWS PoPs in North America & Europe

Section Engineers continue to work on this issue with urgency. Updates will continue to be provided until the issue has been resolved.

We are continuing to investigate this issue. Updates will continue to be provided until the issue has been resolved.

A fix has been implemented, and we are currently monitoring the results.

This incident has been resolved.

Section is currently experiencing experiencing DNS related issues. Engineers are investigating this issue. Updates will continue to be provided on the status of this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

On Nov 9th starting at 03:15 UTC, Section began experiencing degradation in its control plane. This would affect the time it takes for updates to reach the Points of Presence. Engineers are investigating this issue. Updates will continue to be provided on the status of this issue.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Users are unable to create new Projects on the Section platform. We have identified the issue and a fix is in progress.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Section is currently experiencing issues with our KEI Management Console. End-users may experience issues with accessing the console or performing certain functions. Engineers are investigating this issue. Updates will continue to be provided on the status of this issue.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Users that are not already logged in to console.section.io and are attempting to login may experience slowness or errors and will need to retry. Already logged in users should not be affected. Logins to aperture.section.io should not be affected. The issue has been identified and mitigations are being prepared.

This incident has been resolved.

On Wednesday, 2022-09-07 starting at 12:40 UTC, Section began experiencing the KEI API endpoint being unavailable. Engineers are investigating this issue. Updates will continue to be provided on the status of this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

We are currently investigating the issue

We are continuing to investigate this issue.

KEI projects can be created as documented here https://www.section.io/docs/get-started/create-environment/