Agent Versioning temporarily in read only mode
resolved- Started
- Aug 17, 10:35 AM EDT
- Resolved
- Aug 17, 1:33 PM EDT
- Duration
- 2h 58m
Decagon's updates (4)
- update · Aug 17, 10:35 AM EDT
An outage of one of our providers, GitHub, is impacting the ability to save changes on the platform or publish new agent versions. We have temporarily disabled publishing new agent versions while we wait for the impact to be resolved. Current agent versions and underlying agent functionality are not impacted. For any urgent changes, please reach out to your Decagon representative.
- update · Aug 17, 12:20 PM EDT
We are continuing to experience an impact to agent versioning as a result of the GitHub outage. Our team is investigating mitigations in the interim.
- update · Aug 17, 12:55 PM EDT
This degradation has been resolved and we have seen full recovery in the EU. Impacts are still ongoing for the US deployment region.
- resolved · Aug 17, 1:33 PM EDT
The issue has now been resolved and we have fully recovered
What our checks recorded
We checked Decagon 36 times from Decagon's start time to its resolution, once every five minutes. Every one of them reached Decagon's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 194 ms, against 175 ms over the 24 hours before. Decagon posted the incident at Aug 17, 10:35 AM EDT.
Updates are Decagon's own words from its status page (status: resolved); we never add an inferred cause.