APProjects commited on
Commit
fa9ca25
·
verified ·
1 Parent(s): 196c3b3

site refresh (part 3)

Browse files
This view is limited to 50 files because it contains too many changes.   See raw diff
api/v/octopus.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "octopus",
4
  "platform": "statuspage",
5
  "status_url": "https://status.octopus.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This issue has now been resolved. Thank you for your patience whilst we investigated the incident. If you are having any further issues please email support@octopus.com.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-07-31T15:04:03.243Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-07-31T13:32:24.942Z",
@@ -25,7 +25,7 @@
25
  "body": "Azure has resolved this issue.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-07-23T20:28:11.039Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-07-23T16:08:43.170Z",
@@ -38,7 +38,7 @@
38
  "body": "The fix has been live across all Octopus Cloud servers for several weeks now without further issues.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "major",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-08-04T12:23:59.142Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-07-03T00:25:44.406Z",
@@ -51,7 +51,7 @@
51
  "body": "Our upstream provider, Azure in West US2, has resolved their issue. While the issue was ongoing, some Octopus Cloud instances in West US2 may have experienced brief downtime and network communication issues. For more details, see Azure's incident report (Tracking ID: GHRP-84G) at https://azure.status.microsoft/en-us/status/history/.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-05-30T00:38:20.862Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-05-29T06:10:04.469Z",
@@ -64,7 +64,7 @@
64
  "body": "We have pushed out a fix for this issue and it should be rolling out to Octopus Cloud customers over the next few days. \nPlease contact support@octopus.com if you are seeing this issue and we can arrange to get your instance upgraded.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "major",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-05-18T10:49:01.834Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-05-15T12:36:03.385Z",
@@ -77,7 +77,7 @@
77
  "body": "We have not observed any further issues in the West US 2 region so all Octopus Cloud instances in the West US 2 region are using dynamic workers in West US 2 once again.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-05-07T06:40:35.798Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-05-05T13:18:47.601Z",
@@ -90,7 +90,7 @@
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "major",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-04-08T04:11:47.072Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-04-01T08:06:18.168Z",
@@ -103,7 +103,7 @@
103
  "body": "We have identified the cause of this issue and have produced a fix in Octopus version 2026.2.3825. Please email support@octopus.com if you are seeing AWS region endpoint errors in your deployments similar to the one in the title and we can discuss upgrade options.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "major",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-03-30T12:43:39.947Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-03-30T12:43:39.888Z",
@@ -116,7 +116,7 @@
116
  "body": "This incident has been resolved. Please don't hesitate to reach out to our support team if you are still having any related problems.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "major",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-03-25T06:09:24.036Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-03-24T04:13:03.328Z",
@@ -129,7 +129,7 @@
129
  "body": "Email services have now been restored. Please contact support@octopus.com if you encounter any issues with email delivery.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "major",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-02-26T05:47:50.771Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-02-26T01:51:58.000Z",
@@ -142,7 +142,7 @@
142
  "body": "# Summary\n\nOn 2 Feb 2026, between 20:13:34 to 22:56:04 UTC, Octopus Cloud customers in `West US 2` and `West Europe` may have experienced failed deployments or failed runbook runs due to `Ubuntu Dynamic Worker` steps failing on Leasing timeout.\u00a0\n\nThis disruption was caused by Azure failing to provision Virtual Machines across multiple regions - see Azure Issue `FNJ8-VQZ` on [Azure Status History](https://azure.status.microsoft/en-us/status/history/).\u00a0\n\n# Background\n\nOctopus Cloud [Dynamic Workers](https://octopus.com/docs/octopus-cloud/dynamic-worker) are isolated virtual machines that we provide as part of our Octopus Cloud Subscription offering as a way to execute deployment and runbook steps and scripts, without needing to run on the Octopus Server or deployment targets themselves. Customers can use both Windows and Ubuntu Dynamic Workers.\u00a0\n\nOctopus provides a [dynamic worker pool](https://octopus.com/docs/infrastructure/workers/dynamic-worker-pools) of these virtual machine types from which, as required by your deployment/runbook steps, your Octopus Cloud will exclusively lease a freshly provisioned dynamic worker VM for a limited time.\n\n## Dynamic Workers Lifecycle\n\n1. **Provisioning** - a new Azure Virtual Machine is provisioned, using the requested [Dynamic Worker image](https://octopus.com/docs/infrastructure/workers/dynamic-worker-pools#dynamic-worker-images) \\(Windows/Ubuntu with a set of pre-installed tools\\).\n2. **Pool** - the newly created Dynamic Worker \\(VM\\) is placed in a worker pool until an instance requests a Dynamic Worker in one of its deployments/runbooks steps. Each region \\(US, Europe and Australia\\) has different pools for Windows and Ubuntu workers, with additional standby pools that can be turned on in cases of a temporary outage in an Azure region \\(see below\\). Octopus Cloud continuously monitors the pools\u2019 levels and provision new workers automatically to keep them full.\n3. **Leasing** - When a [deployment/runbook that uses a Dynamic Worker](https://octopus.com/docs/infrastructure/workers#where-steps-run) starts, if the instance doesn\u2019t have a leased worker already \\(in which case, it will continue using this worker, extending the worker\u2019s lease for the new run\\), the Octopus Server will request a new worker from the appropriate pool. This worker will be exclusively leased to this instance until it is no longer needed \\(i.e. wasn\u2019t used for an hour\\) or until its maximum lifespan is reached \\(3 days by default\\).\u00a0\n4. **Deletion** - After a worker is no longer needed or it has reached its maximum lifespan, it is considered expired and will be deleted by the system automatically. The next time that the same instance will require a worker, it will lease a new one from the pool \\(see above\\).\n\n## System Resilience & Safeguards\n\nOctopus Cloud implements multiple layers of protection to ensure Dynamic Workers\u2019 availability and minimize customer impact in cases of service disruptions:\n\n* **Pre-provisioned Worker Pools:** We maintain multiple [dynamic worker pools](https://octopus.com/docs/infrastructure/workers/dynamic-worker-pools) \\(for the different virtual machine OS and sizes\\) with ready-to-use workers to provide immediate availability when deployments/runbooks are triggered, rather than waiting for on-demand provisioning. This also provides a safety buffer in cases where we can\u2019t provision new Dynamic Workers due to temporary outages.\n* **Standby Services in Multiple Regions:** We maintain standby Dynamic Worker services in alternate Azure regions that we activate to provide continuity when a primary region experiences issues\n\n# Key Timing\n\n\u200c\n\n# Timeline and Impact\n\nAll dates and times below are in UTC\n\n**Feb 2 2026:**\n\n**18:52:** 1st failed Dynamic Worker provisioning - At this point, our Dynamic Workers Service continued supplying workers successfully from the pools. However, since we couldn\u2019t provision new workers, the pools started depleting.\u00a0\n\n**20:13:** 1st Ubuntu Dynamic Worker lease failed in `West US2` Azure region \\(once the pool was depleted\\) - start of customer impact\n\n**20:47:** Octopus on-call was paged after 3 Dynamic Worker lease requests failed in `West US2`. The on-call then started the incident to investigate the issue\n\n**20:47-21:20**:\u00a0\n\n* Octopus engineers started setting up a Dynamic Workers Service on a different Azure region in the US to mitigate the issue.\u00a0\n* During the investigation we saw that Dynamic Workers were also failing to provision in the `West Europe` and `East Australia` Azure regions. At this point we realized that this was a multi-region outage in Azure and decided to open a support ticket with them.\n* Octopus Engineers turned off non-essential services \\(e.g. Instance Upgrades\\) to preserve the available Dynamic Workers for customer use.\n\n**21:24:** an on-call engineer opened a Sev A support ticket with Azure\n\n**21:31:** We published the initial partial outage alert for Octopus Cloud on [https://status.octopus.com/](https://status.octopus.com/)\u00a0\n\n**21:33:** 1st Dynamic Worker lease failed in `West Europe`\n\n**21:42:** Azure acknowledged the multi-region issue and reported that they are investigating it.\n\n**22:56:** We saw the last Dynamic Worker lease failure. After this time, we were able to provision the required Virtual Machines and return the Dynamic Workers successfully to all lease requests.\n\n**23:46:** After verifying that all Dynamic Worker pools have been restored and we didn\u2019t see any additional provisioning failures, we updated the incident status to \u201cMitigated\u201d, and updated the Status page.\n\n\u200c\n\n**Feb 3 2026:**\n\n**6:05:** Azure confirmed that the issue was fully resolved on their side.\n\n**21:38:** Incident was resolved and Status page updated\n\n\u200c\n\n# Technical Details\n\nOctopus Cloud uses Azure Virtual Machines in order to supply Dynamic Workers to customers. During this Azure outage, we couldn\u2019t provision new Azure Virtual Machines for our Ubuntu Dynamic Workers. Our pre-provisioned Dynamic Workers\u2019 pools continued supplying Dynamic Workers for additional\u00a0\n\n* 1:21 hours in `West US 2` and\u00a0\n* 2:41 hours in `West Europe`\u00a0\n\nbefore they were depleted and customer requests for new Dynamic Workers started failing. It\u2019s worth noting that `East Australia` customers were not impacted because the pools in this region didn\u2019t deplete during the incident. Additionally, customers that already had a Dynamic Worker leased at the time of the outage were not impacted \\(unless their Dynamic Worker expired so a new one was requested during the incident\\).\n\n\u200c\n\nWe made preparations to switch to our Dynamic Workers Standby Service on different Azure regions. However, once we realized that this was a multi-region outage, we decided to revert the switch since it wouldn\u2019t have resolved the issue.\n\n\u200c\n\nOnce we saw that we couldn\u2019t supply Dynamic Workers from our standby regions, we turned off non-essential services \\(e.g. Instance Upgrades\\) to preserve the available Dynamic Workers for customer use.\u00a0\n\n\u200c\n\nOnce Azure mitigated the issue on their side, our system recovered automatically and resumed providing new Dynamic Workers successfully.\u00a0\n\n\u200c\n\n# Remediation\n\nOctopus takes service availability seriously. Despite the difficulty with upstream cloud provider outages, especially ones that are widespread across multiple regions, we fully review and remediate any outages that occur. We do this so that we\u2019re continuously improving and maintaining the best possible service we can.\n\nFollowing our post mortem, we identified the following improvements to our system to help identify and mitigate \\(where possible\\) similar issues earlier:\n\n* **Page an on-call earlier -** \u00a0add an alert to page the on-call when multiple Dynamic Workers in the same region fail to provision. This will allow us to detect similar incidents quicker and give us more time to mitigate the issue, before any Dynamic Worker leases fail and customers are impacted.\n* **Improve our Dynamic Workers Incident Playbook** to identify multi-regions incidents quicker in order to engage Azure support earlier to resolve the root cause of similar incidents.\u00a0\n\n# Conclusion\n\nWe apologize to our customers for any disruption and inconvenience as a result of this incident.\n\nWe have started work on the identified remediations to ensure that we can detect similar incidents more quickly and reduce the impact on our customers as much as possible.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "critical",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2026-02-03T21:38:42.727Z",
147
  "resolved_inferred": false,
148
  "started_at": "2026-02-02T21:31:14.614Z",
@@ -155,7 +155,7 @@
155
  "body": "# Intermittent sign-in issues for Octopus Cloud instances\n\n## Summary\n\nBetween November 25, at 10:24 pm AEST, and November 26, at 12:58 am AEST, customers experienced sporadic issues signing into Octopus Cloud instances. These issues stemmed from a database connection leak, which caused some sign-in requests to time out. We apologize for the inconvenience this has caused our customers and are taking steps to prevent it from happening again.\n\n### Timings\n\nTime to detection: 9hrs 41mins\n\nTime to incident declaration: 9hrs 41mins\n\nTime to resolution: 12hrs 15mins\n\n## What happened?\n\n\\(All dates and times below are in AEST\\)\n\n### November 25\n\n**12:43 pm** We deployed a change to our authorization service. This change introduced a bug resulting in database connection leaks. The connection leak only became apparent in high-traffic scenarios, which our current test suite doesn't replicate. As a result, our test suite didn't detect the issue.\n\n**10:24 pm** A DevOps Support Engineer declared an incident after receiving reports from customers that they were having difficulty signing into Octopus Cloud instances.\n\n**10:24 pm - 11:41 pm** Investigations showed that the issue was due to database connection timeouts.\n\n**11:42 pm** Temporary mitigations implemented, including restarting services to release database connections.\n\n**11:42 pm - 11:59 pm** Effects of mitigations observed and deemed successful. Incident marked as mitigated.\n\n### November 26\n\n**12:00 am - 12:57 am** Incident responders continue to watch systems.\n\n**12:58 am** Mitigation steps considered successful, and the incident marked as resolved.\n\n**6:55 am** Root cause of database connection timeouts identified as a connection leak.\n\n**6:55 am - 8:33 am** Permanent fix implemented and deployed.\n\n## Remediation and next steps\n\nWe deployed a new service version to remove the database connection leak. We have also conducted an incident review to identify process improvements to prevent this from occurring in the future. We continue to work towards improving the reliability and security of our authentication and authorization services.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "major",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2025-11-25T14:57:46.057Z",
160
  "resolved_inferred": false,
161
  "started_at": "2025-11-25T12:34:28.801Z",
@@ -168,7 +168,7 @@
168
  "body": "We have observed no further errors stemming from this issue.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2025-11-19T00:47:43.194Z",
173
  "resolved_inferred": false,
174
  "started_at": "2025-11-18T21:11:25.133Z",
@@ -181,7 +181,7 @@
181
  "body": "All Octopus services affected by this outage are now operational.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "critical",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2025-10-30T01:13:36.031Z",
186
  "resolved_inferred": false,
187
  "started_at": "2025-10-29T16:31:49.564Z",
@@ -194,7 +194,7 @@
194
  "body": "Docker Hub have resolved their incident and we have not observed any further issues",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "major",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2025-10-21T01:11:53.190Z",
199
  "resolved_inferred": false,
200
  "started_at": "2025-10-20T07:34:33.883Z",
@@ -207,7 +207,7 @@
207
  "body": "This has been resolved. All missing tags have been published to DockerHub and we are seeing successful deployments using these new tags.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "major",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2025-10-13T00:24:17.344Z",
212
  "resolved_inferred": false,
213
  "started_at": "2025-10-12T23:43:06.000Z",
@@ -220,7 +220,7 @@
220
  "body": "# **Incident Summary**\n\nDocker Hub experienced authentication issues that prevented access to container images, resulting in deployment failures for projects relying on those images.\n\n## **What We're Doing**\n\nFollowing this incident, we've identified several improvements to enhance service resilience and customer communication:\n\n### **Visibility & Monitoring**\n\n* Communicate third-party service outages more clearly on our status page\n* Explore in-app messaging to alert customers during service disruptions\n\n### **Resilience & Good Practices**\n\n* Review image retrieval reliability and address identified risks\n* Share good practices with customers to help reduce impacts when Docker Hub is unavailable",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "major",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2025-09-25T04:18:59.632Z",
225
  "resolved_inferred": false,
226
  "started_at": "2025-09-25T01:06:30.966Z",
@@ -233,7 +233,7 @@
233
  "body": "The downstream issue with Azure CLI login commands has been resolved by Azure.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2025-09-15T06:05:33.167Z",
238
  "resolved_inferred": false,
239
  "started_at": "2025-09-15T03:11:19.350Z",
@@ -246,7 +246,7 @@
246
  "body": "This issue is resolved, please reach out to https://octopus.com/support if you are still experiencing deployments that fail to start.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "minor",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2025-09-05T03:50:03.134Z",
251
  "resolved_inferred": false,
252
  "started_at": "2025-09-04T02:31:49.720Z",
 
3
  "slug": "octopus",
4
  "platform": "statuspage",
5
  "status_url": "https://status.octopus.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This issue has now been resolved. Thank you for your patience whilst we investigated the incident. If you are having any further issues please email support@octopus.com.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-07-31T15:04:03.243Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-07-31T13:32:24.942Z",
 
25
  "body": "Azure has resolved this issue.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-07-23T20:28:11.039Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-07-23T16:08:43.170Z",
 
38
  "body": "The fix has been live across all Octopus Cloud servers for several weeks now without further issues.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "major",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-08-04T12:23:59.142Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-07-03T00:25:44.406Z",
 
51
  "body": "Our upstream provider, Azure in West US2, has resolved their issue. While the issue was ongoing, some Octopus Cloud instances in West US2 may have experienced brief downtime and network communication issues. For more details, see Azure's incident report (Tracking ID: GHRP-84G) at https://azure.status.microsoft/en-us/status/history/.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-05-30T00:38:20.862Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-05-29T06:10:04.469Z",
 
64
  "body": "We have pushed out a fix for this issue and it should be rolling out to Octopus Cloud customers over the next few days. \nPlease contact support@octopus.com if you are seeing this issue and we can arrange to get your instance upgraded.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "major",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-05-18T10:49:01.834Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-05-15T12:36:03.385Z",
 
77
  "body": "We have not observed any further issues in the West US 2 region so all Octopus Cloud instances in the West US 2 region are using dynamic workers in West US 2 once again.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-05-07T06:40:35.798Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-05-05T13:18:47.601Z",
 
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "major",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-04-08T04:11:47.072Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-04-01T08:06:18.168Z",
 
103
  "body": "We have identified the cause of this issue and have produced a fix in Octopus version 2026.2.3825. Please email support@octopus.com if you are seeing AWS region endpoint errors in your deployments similar to the one in the title and we can discuss upgrade options.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "major",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-03-30T12:43:39.947Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-03-30T12:43:39.888Z",
 
116
  "body": "This incident has been resolved. Please don't hesitate to reach out to our support team if you are still having any related problems.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "major",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-03-25T06:09:24.036Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-03-24T04:13:03.328Z",
 
129
  "body": "Email services have now been restored. Please contact support@octopus.com if you encounter any issues with email delivery.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "major",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-02-26T05:47:50.771Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-02-26T01:51:58.000Z",
 
142
  "body": "# Summary\n\nOn 2 Feb 2026, between 20:13:34 to 22:56:04 UTC, Octopus Cloud customers in `West US 2` and `West Europe` may have experienced failed deployments or failed runbook runs due to `Ubuntu Dynamic Worker` steps failing on Leasing timeout.\u00a0\n\nThis disruption was caused by Azure failing to provision Virtual Machines across multiple regions - see Azure Issue `FNJ8-VQZ` on [Azure Status History](https://azure.status.microsoft/en-us/status/history/).\u00a0\n\n# Background\n\nOctopus Cloud [Dynamic Workers](https://octopus.com/docs/octopus-cloud/dynamic-worker) are isolated virtual machines that we provide as part of our Octopus Cloud Subscription offering as a way to execute deployment and runbook steps and scripts, without needing to run on the Octopus Server or deployment targets themselves. Customers can use both Windows and Ubuntu Dynamic Workers.\u00a0\n\nOctopus provides a [dynamic worker pool](https://octopus.com/docs/infrastructure/workers/dynamic-worker-pools) of these virtual machine types from which, as required by your deployment/runbook steps, your Octopus Cloud will exclusively lease a freshly provisioned dynamic worker VM for a limited time.\n\n## Dynamic Workers Lifecycle\n\n1. **Provisioning** - a new Azure Virtual Machine is provisioned, using the requested [Dynamic Worker image](https://octopus.com/docs/infrastructure/workers/dynamic-worker-pools#dynamic-worker-images) \\(Windows/Ubuntu with a set of pre-installed tools\\).\n2. **Pool** - the newly created Dynamic Worker \\(VM\\) is placed in a worker pool until an instance requests a Dynamic Worker in one of its deployments/runbooks steps. Each region \\(US, Europe and Australia\\) has different pools for Windows and Ubuntu workers, with additional standby pools that can be turned on in cases of a temporary outage in an Azure region \\(see below\\). Octopus Cloud continuously monitors the pools\u2019 levels and provision new workers automatically to keep them full.\n3. **Leasing** - When a [deployment/runbook that uses a Dynamic Worker](https://octopus.com/docs/infrastructure/workers#where-steps-run) starts, if the instance doesn\u2019t have a leased worker already \\(in which case, it will continue using this worker, extending the worker\u2019s lease for the new run\\), the Octopus Server will request a new worker from the appropriate pool. This worker will be exclusively leased to this instance until it is no longer needed \\(i.e. wasn\u2019t used for an hour\\) or until its maximum lifespan is reached \\(3 days by default\\).\u00a0\n4. **Deletion** - After a worker is no longer needed or it has reached its maximum lifespan, it is considered expired and will be deleted by the system automatically. The next time that the same instance will require a worker, it will lease a new one from the pool \\(see above\\).\n\n## System Resilience & Safeguards\n\nOctopus Cloud implements multiple layers of protection to ensure Dynamic Workers\u2019 availability and minimize customer impact in cases of service disruptions:\n\n* **Pre-provisioned Worker Pools:** We maintain multiple [dynamic worker pools](https://octopus.com/docs/infrastructure/workers/dynamic-worker-pools) \\(for the different virtual machine OS and sizes\\) with ready-to-use workers to provide immediate availability when deployments/runbooks are triggered, rather than waiting for on-demand provisioning. This also provides a safety buffer in cases where we can\u2019t provision new Dynamic Workers due to temporary outages.\n* **Standby Services in Multiple Regions:** We maintain standby Dynamic Worker services in alternate Azure regions that we activate to provide continuity when a primary region experiences issues\n\n# Key Timing\n\n\u200c\n\n# Timeline and Impact\n\nAll dates and times below are in UTC\n\n**Feb 2 2026:**\n\n**18:52:** 1st failed Dynamic Worker provisioning - At this point, our Dynamic Workers Service continued supplying workers successfully from the pools. However, since we couldn\u2019t provision new workers, the pools started depleting.\u00a0\n\n**20:13:** 1st Ubuntu Dynamic Worker lease failed in `West US2` Azure region \\(once the pool was depleted\\) - start of customer impact\n\n**20:47:** Octopus on-call was paged after 3 Dynamic Worker lease requests failed in `West US2`. The on-call then started the incident to investigate the issue\n\n**20:47-21:20**:\u00a0\n\n* Octopus engineers started setting up a Dynamic Workers Service on a different Azure region in the US to mitigate the issue.\u00a0\n* During the investigation we saw that Dynamic Workers were also failing to provision in the `West Europe` and `East Australia` Azure regions. At this point we realized that this was a multi-region outage in Azure and decided to open a support ticket with them.\n* Octopus Engineers turned off non-essential services \\(e.g. Instance Upgrades\\) to preserve the available Dynamic Workers for customer use.\n\n**21:24:** an on-call engineer opened a Sev A support ticket with Azure\n\n**21:31:** We published the initial partial outage alert for Octopus Cloud on [https://status.octopus.com/](https://status.octopus.com/)\u00a0\n\n**21:33:** 1st Dynamic Worker lease failed in `West Europe`\n\n**21:42:** Azure acknowledged the multi-region issue and reported that they are investigating it.\n\n**22:56:** We saw the last Dynamic Worker lease failure. After this time, we were able to provision the required Virtual Machines and return the Dynamic Workers successfully to all lease requests.\n\n**23:46:** After verifying that all Dynamic Worker pools have been restored and we didn\u2019t see any additional provisioning failures, we updated the incident status to \u201cMitigated\u201d, and updated the Status page.\n\n\u200c\n\n**Feb 3 2026:**\n\n**6:05:** Azure confirmed that the issue was fully resolved on their side.\n\n**21:38:** Incident was resolved and Status page updated\n\n\u200c\n\n# Technical Details\n\nOctopus Cloud uses Azure Virtual Machines in order to supply Dynamic Workers to customers. During this Azure outage, we couldn\u2019t provision new Azure Virtual Machines for our Ubuntu Dynamic Workers. Our pre-provisioned Dynamic Workers\u2019 pools continued supplying Dynamic Workers for additional\u00a0\n\n* 1:21 hours in `West US 2` and\u00a0\n* 2:41 hours in `West Europe`\u00a0\n\nbefore they were depleted and customer requests for new Dynamic Workers started failing. It\u2019s worth noting that `East Australia` customers were not impacted because the pools in this region didn\u2019t deplete during the incident. Additionally, customers that already had a Dynamic Worker leased at the time of the outage were not impacted \\(unless their Dynamic Worker expired so a new one was requested during the incident\\).\n\n\u200c\n\nWe made preparations to switch to our Dynamic Workers Standby Service on different Azure regions. However, once we realized that this was a multi-region outage, we decided to revert the switch since it wouldn\u2019t have resolved the issue.\n\n\u200c\n\nOnce we saw that we couldn\u2019t supply Dynamic Workers from our standby regions, we turned off non-essential services \\(e.g. Instance Upgrades\\) to preserve the available Dynamic Workers for customer use.\u00a0\n\n\u200c\n\nOnce Azure mitigated the issue on their side, our system recovered automatically and resumed providing new Dynamic Workers successfully.\u00a0\n\n\u200c\n\n# Remediation\n\nOctopus takes service availability seriously. Despite the difficulty with upstream cloud provider outages, especially ones that are widespread across multiple regions, we fully review and remediate any outages that occur. We do this so that we\u2019re continuously improving and maintaining the best possible service we can.\n\nFollowing our post mortem, we identified the following improvements to our system to help identify and mitigate \\(where possible\\) similar issues earlier:\n\n* **Page an on-call earlier -** \u00a0add an alert to page the on-call when multiple Dynamic Workers in the same region fail to provision. This will allow us to detect similar incidents quicker and give us more time to mitigate the issue, before any Dynamic Worker leases fail and customers are impacted.\n* **Improve our Dynamic Workers Incident Playbook** to identify multi-regions incidents quicker in order to engage Azure support earlier to resolve the root cause of similar incidents.\u00a0\n\n# Conclusion\n\nWe apologize to our customers for any disruption and inconvenience as a result of this incident.\n\nWe have started work on the identified remediations to ensure that we can detect similar incidents more quickly and reduce the impact on our customers as much as possible.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "critical",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2026-02-03T21:38:42.727Z",
147
  "resolved_inferred": false,
148
  "started_at": "2026-02-02T21:31:14.614Z",
 
155
  "body": "# Intermittent sign-in issues for Octopus Cloud instances\n\n## Summary\n\nBetween November 25, at 10:24 pm AEST, and November 26, at 12:58 am AEST, customers experienced sporadic issues signing into Octopus Cloud instances. These issues stemmed from a database connection leak, which caused some sign-in requests to time out. We apologize for the inconvenience this has caused our customers and are taking steps to prevent it from happening again.\n\n### Timings\n\nTime to detection: 9hrs 41mins\n\nTime to incident declaration: 9hrs 41mins\n\nTime to resolution: 12hrs 15mins\n\n## What happened?\n\n\\(All dates and times below are in AEST\\)\n\n### November 25\n\n**12:43 pm** We deployed a change to our authorization service. This change introduced a bug resulting in database connection leaks. The connection leak only became apparent in high-traffic scenarios, which our current test suite doesn't replicate. As a result, our test suite didn't detect the issue.\n\n**10:24 pm** A DevOps Support Engineer declared an incident after receiving reports from customers that they were having difficulty signing into Octopus Cloud instances.\n\n**10:24 pm - 11:41 pm** Investigations showed that the issue was due to database connection timeouts.\n\n**11:42 pm** Temporary mitigations implemented, including restarting services to release database connections.\n\n**11:42 pm - 11:59 pm** Effects of mitigations observed and deemed successful. Incident marked as mitigated.\n\n### November 26\n\n**12:00 am - 12:57 am** Incident responders continue to watch systems.\n\n**12:58 am** Mitigation steps considered successful, and the incident marked as resolved.\n\n**6:55 am** Root cause of database connection timeouts identified as a connection leak.\n\n**6:55 am - 8:33 am** Permanent fix implemented and deployed.\n\n## Remediation and next steps\n\nWe deployed a new service version to remove the database connection leak. We have also conducted an incident review to identify process improvements to prevent this from occurring in the future. We continue to work towards improving the reliability and security of our authentication and authorization services.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "major",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2025-11-25T14:57:46.057Z",
160
  "resolved_inferred": false,
161
  "started_at": "2025-11-25T12:34:28.801Z",
 
168
  "body": "We have observed no further errors stemming from this issue.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2025-11-19T00:47:43.194Z",
173
  "resolved_inferred": false,
174
  "started_at": "2025-11-18T21:11:25.133Z",
 
181
  "body": "All Octopus services affected by this outage are now operational.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "critical",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2025-10-30T01:13:36.031Z",
186
  "resolved_inferred": false,
187
  "started_at": "2025-10-29T16:31:49.564Z",
 
194
  "body": "Docker Hub have resolved their incident and we have not observed any further issues",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "major",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2025-10-21T01:11:53.190Z",
199
  "resolved_inferred": false,
200
  "started_at": "2025-10-20T07:34:33.883Z",
 
207
  "body": "This has been resolved. All missing tags have been published to DockerHub and we are seeing successful deployments using these new tags.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "major",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2025-10-13T00:24:17.344Z",
212
  "resolved_inferred": false,
213
  "started_at": "2025-10-12T23:43:06.000Z",
 
220
  "body": "# **Incident Summary**\n\nDocker Hub experienced authentication issues that prevented access to container images, resulting in deployment failures for projects relying on those images.\n\n## **What We're Doing**\n\nFollowing this incident, we've identified several improvements to enhance service resilience and customer communication:\n\n### **Visibility & Monitoring**\n\n* Communicate third-party service outages more clearly on our status page\n* Explore in-app messaging to alert customers during service disruptions\n\n### **Resilience & Good Practices**\n\n* Review image retrieval reliability and address identified risks\n* Share good practices with customers to help reduce impacts when Docker Hub is unavailable",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "major",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2025-09-25T04:18:59.632Z",
225
  "resolved_inferred": false,
226
  "started_at": "2025-09-25T01:06:30.966Z",
 
233
  "body": "The downstream issue with Azure CLI login commands has been resolved by Azure.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2025-09-15T06:05:33.167Z",
238
  "resolved_inferred": false,
239
  "started_at": "2025-09-15T03:11:19.350Z",
 
246
  "body": "This issue is resolved, please reach out to https://octopus.com/support if you are still experiencing deployments that fail to start.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "minor",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2025-09-05T03:50:03.134Z",
251
  "resolved_inferred": false,
252
  "started_at": "2025-09-04T02:31:49.720Z",
api/v/officernd.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "officernd",
4
  "platform": "statuspage",
5
  "status_url": "https://status.officernd.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "none",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-06-23T19:21:41.312+03:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-06-23T17:58:51.713+03:00",
@@ -25,7 +25,7 @@
25
  "body": "DataHub report fails to load without proper initialization",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "none",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-05-18T14:30:00.000+03:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-05-18T14:30:00.000+03:00",
@@ -38,7 +38,7 @@
38
  "body": "The system is currently experiencing a degradation in performance, resulting in slower response times",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "none",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-01-01T06:30:00.000+02:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-01-01T06:30:00.000+02:00",
@@ -51,7 +51,7 @@
51
  "body": "We've experienced Degraded performance in our Flex product (Admin Portal and Members Portal) for four (4) minutes in total. \nWe are investigating!",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2025-12-10T13:00:00.000+02:00",
56
  "resolved_inferred": false,
57
  "started_at": "2025-12-10T13:00:00.000+02:00",
@@ -64,7 +64,7 @@
64
  "body": "Cloudflare has confirmed the issue is resolved, and custom domains are now functioning normally again.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "critical",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2025-11-18T21:18:51.341+02:00",
69
  "resolved_inferred": false,
70
  "started_at": "2025-11-18T13:48:47.790+02:00",
@@ -77,7 +77,7 @@
77
  "body": "We identified a platform outage that lasted approximately two minutes, affecting mainly the Flex Admin portal.\nThe platform's performance recovered fully within 20 minutes.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "none",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2025-11-12T15:00:00.000+02:00",
82
  "resolved_inferred": false,
83
  "started_at": "2025-11-12T15:00:00.000+02:00",
@@ -90,7 +90,7 @@
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2025-10-27T11:14:07.029+02:00",
95
  "resolved_inferred": false,
96
  "started_at": "2025-10-27T09:55:00.410+02:00",
@@ -103,7 +103,7 @@
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2025-09-30T16:39:54.134+03:00",
108
  "resolved_inferred": false,
109
  "started_at": "2025-09-30T16:06:50.154+03:00",
@@ -116,7 +116,7 @@
116
  "body": "The incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2025-09-01T19:21:37.532+03:00",
121
  "resolved_inferred": false,
122
  "started_at": "2025-09-01T13:48:38.488+03:00",
 
3
  "slug": "officernd",
4
  "platform": "statuspage",
5
  "status_url": "https://status.officernd.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "none",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-06-23T19:21:41.312+03:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-06-23T17:58:51.713+03:00",
 
25
  "body": "DataHub report fails to load without proper initialization",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "none",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-05-18T14:30:00.000+03:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-05-18T14:30:00.000+03:00",
 
38
  "body": "The system is currently experiencing a degradation in performance, resulting in slower response times",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "none",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-01-01T06:30:00.000+02:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-01-01T06:30:00.000+02:00",
 
51
  "body": "We've experienced Degraded performance in our Flex product (Admin Portal and Members Portal) for four (4) minutes in total. \nWe are investigating!",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2025-12-10T13:00:00.000+02:00",
56
  "resolved_inferred": false,
57
  "started_at": "2025-12-10T13:00:00.000+02:00",
 
64
  "body": "Cloudflare has confirmed the issue is resolved, and custom domains are now functioning normally again.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "critical",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2025-11-18T21:18:51.341+02:00",
69
  "resolved_inferred": false,
70
  "started_at": "2025-11-18T13:48:47.790+02:00",
 
77
  "body": "We identified a platform outage that lasted approximately two minutes, affecting mainly the Flex Admin portal.\nThe platform's performance recovered fully within 20 minutes.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "none",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2025-11-12T15:00:00.000+02:00",
82
  "resolved_inferred": false,
83
  "started_at": "2025-11-12T15:00:00.000+02:00",
 
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2025-10-27T11:14:07.029+02:00",
95
  "resolved_inferred": false,
96
  "started_at": "2025-10-27T09:55:00.410+02:00",
 
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2025-09-30T16:39:54.134+03:00",
108
  "resolved_inferred": false,
109
  "started_at": "2025-09-30T16:06:50.154+03:00",
 
116
  "body": "The incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2025-09-01T19:21:37.532+03:00",
121
  "resolved_inferred": false,
122
  "started_at": "2025-09-01T13:48:38.488+03:00",
api/v/one.json CHANGED
@@ -3,20 +3,20 @@
3
  "slug": "one",
4
  "platform": "statuspage",
5
  "status_url": "https://status.one.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
10
  "incidents": [
11
  {
12
- "body": "Due to temporary capacity issues at Microsoft, emails to Microsoft servers may be delivered with a delay.\n\nIf you receive a bounce with the subject \u201cDelivery delayed\u201d, this is an expected consequence of the current outage. No action is required on your part. \nThe email will be delivered automatically as soon as the receiving email provider, Microsoft, has resolved the issue.",
13
  "first_seen": "2026-09-04T11:14:03Z",
14
  "impact": "none",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "started_at": "2026-09-04T12:52:54.208+02:00",
17
- "state": "identified",
18
  "title": "Email delivery issues with Microsoft",
19
- "updated_at": "2026-09-04T12:52:54.250+02:00",
20
  "url": "https://stspg.io/s8wl3dpgjzym"
21
  },
22
  {
@@ -36,7 +36,7 @@
36
  "body": "This incident has been resolved.",
37
  "first_seen": "2026-09-04T07:06:16Z",
38
  "impact": "minor",
39
- "last_seen": "2026-09-04T12:24:18Z",
40
  "resolved_at": "2026-09-02T13:40:46.596+02:00",
41
  "resolved_inferred": false,
42
  "started_at": "2026-09-02T12:14:30.646+02:00",
@@ -49,7 +49,7 @@
49
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://help.one.com/hc/en-us/requests/new",
50
  "first_seen": "2026-09-04T07:06:16Z",
51
  "impact": "minor",
52
- "last_seen": "2026-09-04T12:24:18Z",
53
  "resolved_at": "2026-09-02T11:44:53.815+02:00",
54
  "resolved_inferred": false,
55
  "started_at": "2026-09-02T11:15:17.373+02:00",
@@ -62,7 +62,7 @@
62
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://help.one.com/hc/en-us/requests/new",
63
  "first_seen": "2026-09-04T07:06:16Z",
64
  "impact": "minor",
65
- "last_seen": "2026-09-04T12:24:18Z",
66
  "resolved_at": "2026-09-01T09:45:54.684+02:00",
67
  "resolved_inferred": false,
68
  "started_at": "2026-09-01T09:14:19.765+02:00",
@@ -75,7 +75,7 @@
75
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://www.one.com/chat.",
76
  "first_seen": "2026-09-04T07:06:16Z",
77
  "impact": "minor",
78
- "last_seen": "2026-09-04T12:24:18Z",
79
  "resolved_at": "2026-09-01T08:26:34.301+02:00",
80
  "resolved_inferred": false,
81
  "started_at": "2026-09-01T07:23:18.000+02:00",
@@ -88,7 +88,7 @@
88
  "body": "Calendar access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://www.one.com/chat.",
89
  "first_seen": "2026-09-04T07:06:16Z",
90
  "impact": "minor",
91
- "last_seen": "2026-09-04T12:24:18Z",
92
  "resolved_at": "2026-08-31T12:45:33.679+02:00",
93
  "resolved_inferred": false,
94
  "started_at": "2026-08-31T10:42:26.201+02:00",
@@ -101,7 +101,7 @@
101
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://www.one.com/chat.",
102
  "first_seen": "2026-09-04T07:06:16Z",
103
  "impact": "critical",
104
- "last_seen": "2026-09-04T12:24:18Z",
105
  "resolved_at": "2026-08-31T10:35:44.106+02:00",
106
  "resolved_inferred": false,
107
  "started_at": "2026-08-31T10:30:19.297+02:00",
@@ -114,7 +114,7 @@
114
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://www.one.com/chat.",
115
  "first_seen": "2026-09-04T07:06:16Z",
116
  "impact": "minor",
117
- "last_seen": "2026-09-04T12:24:18Z",
118
  "resolved_at": "2026-08-03T11:39:04.788+02:00",
119
  "resolved_inferred": false,
120
  "started_at": "2026-08-03T11:13:12.344+02:00",
@@ -127,7 +127,7 @@
127
  "body": "The scheduled maintenance has been completed.",
128
  "first_seen": "2026-09-04T07:06:16Z",
129
  "impact": "minor",
130
- "last_seen": "2026-09-04T12:24:18Z",
131
  "resolved_at": "2026-07-17T23:52:23.588+02:00",
132
  "resolved_inferred": false,
133
  "started_at": "2026-07-17T16:33:18.000+02:00",
@@ -140,7 +140,7 @@
140
  "body": "Access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://help.one.com/hc/en-us/requests/new",
141
  "first_seen": "2026-09-04T07:06:16Z",
142
  "impact": "minor",
143
- "last_seen": "2026-09-04T12:24:18Z",
144
  "resolved_at": "2026-06-24T11:24:48.844+02:00",
145
  "resolved_inferred": false,
146
  "started_at": "2026-06-24T11:04:37.459+02:00",
@@ -153,7 +153,7 @@
153
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://www.one.com/en-gb/about/contact-us/.",
154
  "first_seen": "2026-09-04T07:06:16Z",
155
  "impact": "minor",
156
- "last_seen": "2026-09-04T12:24:18Z",
157
  "resolved_at": "2026-06-09T08:55:47.836+02:00",
158
  "resolved_inferred": false,
159
  "started_at": "2026-06-09T08:43:21.188+02:00",
@@ -166,7 +166,7 @@
166
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://help.one.com/hc/en-us/requests/new.",
167
  "first_seen": "2026-09-04T07:06:16Z",
168
  "impact": "minor",
169
- "last_seen": "2026-09-04T12:24:18Z",
170
  "resolved_at": "2026-05-08T12:34:31.692+02:00",
171
  "resolved_inferred": false,
172
  "started_at": "2026-05-08T11:21:20.272+02:00",
@@ -179,7 +179,7 @@
179
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://www.one.com/chat.",
180
  "first_seen": "2026-09-04T07:06:16Z",
181
  "impact": "major",
182
- "last_seen": "2026-09-04T12:24:18Z",
183
  "resolved_at": "2026-04-27T13:53:18.135+02:00",
184
  "resolved_inferred": false,
185
  "started_at": "2026-04-27T13:47:02.895+02:00",
@@ -192,7 +192,7 @@
192
  "body": "Control panel access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://www.one.com/chat.",
193
  "first_seen": "2026-09-04T07:06:16Z",
194
  "impact": "major",
195
- "last_seen": "2026-09-04T12:24:18Z",
196
  "resolved_at": "2026-04-24T11:12:37.000+02:00",
197
  "resolved_inferred": false,
198
  "started_at": "2026-04-24T10:53:19.945+02:00",
@@ -205,7 +205,7 @@
205
  "body": "We are currently experiencing an issue where the control panel is not loading for some customers.\n\nOur technicians are aware of the problem and are actively working to identify the root cause and implement a solution as quickly as possible.\n\nWe will provide further updates as more information becomes available.\n\nThank you for your patience.",
206
  "first_seen": "2026-09-04T07:06:16Z",
207
  "impact": "none",
208
- "last_seen": "2026-09-04T12:24:18Z",
209
  "resolved_at": "2026-04-20T09:30:00.000+02:00",
210
  "resolved_inferred": false,
211
  "started_at": "2026-04-20T09:30:00.000+02:00",
@@ -218,7 +218,7 @@
218
  "body": "Resolved\nWebmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please get in touch with us on chat or email here: https://www.one.com/chat.\nPosted Feb 13, 2026 - 17:11 CET\n\nMonitoring\nA fix has been implemented, and the issue seems to be resolved. \n\nWe are currently monitoring the situation to ensure continued stability.\nPosted Feb 13, 2026 - 16:04 CET\n\nIdentified\nThe prevoius issue with webmail has reappeared, we are working on fixing it in a different way\nPosted Feb 13, 2026 - 14:50 CET\n\nMonitoring\nA fix has been implemented, and we will monitor the situation for a while.\nPosted Feb 13, 2026 - 14:26 CET\n\nIdentified\nThe issue has been identifed, and a fix is being worked on as we speak.\nPosted Feb 13, 2026 - 13:38 CET\n\nInvestigating\nWe are currently investigating an issue affecting our webmail service.\n\nA further update will be provided no later than 13:45 CET",
219
  "first_seen": "2026-09-04T07:06:16Z",
220
  "impact": "none",
221
- "last_seen": "2026-09-04T12:24:18Z",
222
  "resolved_at": "2026-02-13T13:14:00.000+01:00",
223
  "resolved_inferred": false,
224
  "started_at": "2026-02-13T13:14:00.000+01:00",
 
3
  "slug": "one",
4
  "platform": "statuspage",
5
  "status_url": "https://status.one.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
10
  "incidents": [
11
  {
12
+ "body": "Microsoft is accepting incoming emails again. \n\nMessages that previously received a \u201cDelivery delayed\u201d notice due to delays on Microsoft\u2019s side are now being delivered gradually. \n\nWe will continue monitoring the situation until all backlogs have been processed.",
13
  "first_seen": "2026-09-04T11:14:03Z",
14
  "impact": "none",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "started_at": "2026-09-04T12:52:54.208+02:00",
17
+ "state": "monitoring",
18
  "title": "Email delivery issues with Microsoft",
19
+ "updated_at": "2026-09-04T15:47:25.840+02:00",
20
  "url": "https://stspg.io/s8wl3dpgjzym"
21
  },
22
  {
 
36
  "body": "This incident has been resolved.",
37
  "first_seen": "2026-09-04T07:06:16Z",
38
  "impact": "minor",
39
+ "last_seen": "2026-09-04T14:19:03Z",
40
  "resolved_at": "2026-09-02T13:40:46.596+02:00",
41
  "resolved_inferred": false,
42
  "started_at": "2026-09-02T12:14:30.646+02:00",
 
49
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://help.one.com/hc/en-us/requests/new",
50
  "first_seen": "2026-09-04T07:06:16Z",
51
  "impact": "minor",
52
+ "last_seen": "2026-09-04T14:19:03Z",
53
  "resolved_at": "2026-09-02T11:44:53.815+02:00",
54
  "resolved_inferred": false,
55
  "started_at": "2026-09-02T11:15:17.373+02:00",
 
62
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://help.one.com/hc/en-us/requests/new",
63
  "first_seen": "2026-09-04T07:06:16Z",
64
  "impact": "minor",
65
+ "last_seen": "2026-09-04T14:19:03Z",
66
  "resolved_at": "2026-09-01T09:45:54.684+02:00",
67
  "resolved_inferred": false,
68
  "started_at": "2026-09-01T09:14:19.765+02:00",
 
75
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://www.one.com/chat.",
76
  "first_seen": "2026-09-04T07:06:16Z",
77
  "impact": "minor",
78
+ "last_seen": "2026-09-04T14:19:03Z",
79
  "resolved_at": "2026-09-01T08:26:34.301+02:00",
80
  "resolved_inferred": false,
81
  "started_at": "2026-09-01T07:23:18.000+02:00",
 
88
  "body": "Calendar access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://www.one.com/chat.",
89
  "first_seen": "2026-09-04T07:06:16Z",
90
  "impact": "minor",
91
+ "last_seen": "2026-09-04T14:19:03Z",
92
  "resolved_at": "2026-08-31T12:45:33.679+02:00",
93
  "resolved_inferred": false,
94
  "started_at": "2026-08-31T10:42:26.201+02:00",
 
101
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://www.one.com/chat.",
102
  "first_seen": "2026-09-04T07:06:16Z",
103
  "impact": "critical",
104
+ "last_seen": "2026-09-04T14:19:03Z",
105
  "resolved_at": "2026-08-31T10:35:44.106+02:00",
106
  "resolved_inferred": false,
107
  "started_at": "2026-08-31T10:30:19.297+02:00",
 
114
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://www.one.com/chat.",
115
  "first_seen": "2026-09-04T07:06:16Z",
116
  "impact": "minor",
117
+ "last_seen": "2026-09-04T14:19:03Z",
118
  "resolved_at": "2026-08-03T11:39:04.788+02:00",
119
  "resolved_inferred": false,
120
  "started_at": "2026-08-03T11:13:12.344+02:00",
 
127
  "body": "The scheduled maintenance has been completed.",
128
  "first_seen": "2026-09-04T07:06:16Z",
129
  "impact": "minor",
130
+ "last_seen": "2026-09-04T14:19:03Z",
131
  "resolved_at": "2026-07-17T23:52:23.588+02:00",
132
  "resolved_inferred": false,
133
  "started_at": "2026-07-17T16:33:18.000+02:00",
 
140
  "body": "Access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://help.one.com/hc/en-us/requests/new",
141
  "first_seen": "2026-09-04T07:06:16Z",
142
  "impact": "minor",
143
+ "last_seen": "2026-09-04T14:19:03Z",
144
  "resolved_at": "2026-06-24T11:24:48.844+02:00",
145
  "resolved_inferred": false,
146
  "started_at": "2026-06-24T11:04:37.459+02:00",
 
153
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://www.one.com/en-gb/about/contact-us/.",
154
  "first_seen": "2026-09-04T07:06:16Z",
155
  "impact": "minor",
156
+ "last_seen": "2026-09-04T14:19:03Z",
157
  "resolved_at": "2026-06-09T08:55:47.836+02:00",
158
  "resolved_inferred": false,
159
  "started_at": "2026-06-09T08:43:21.188+02:00",
 
166
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://help.one.com/hc/en-us/requests/new.",
167
  "first_seen": "2026-09-04T07:06:16Z",
168
  "impact": "minor",
169
+ "last_seen": "2026-09-04T14:19:03Z",
170
  "resolved_at": "2026-05-08T12:34:31.692+02:00",
171
  "resolved_inferred": false,
172
  "started_at": "2026-05-08T11:21:20.272+02:00",
 
179
  "body": "Webmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://www.one.com/chat.",
180
  "first_seen": "2026-09-04T07:06:16Z",
181
  "impact": "major",
182
+ "last_seen": "2026-09-04T14:19:03Z",
183
  "resolved_at": "2026-04-27T13:53:18.135+02:00",
184
  "resolved_inferred": false,
185
  "started_at": "2026-04-27T13:47:02.895+02:00",
 
192
  "body": "Control panel access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please contact us on chat or email here: https://www.one.com/chat.",
193
  "first_seen": "2026-09-04T07:06:16Z",
194
  "impact": "major",
195
+ "last_seen": "2026-09-04T14:19:03Z",
196
  "resolved_at": "2026-04-24T11:12:37.000+02:00",
197
  "resolved_inferred": false,
198
  "started_at": "2026-04-24T10:53:19.945+02:00",
 
205
  "body": "We are currently experiencing an issue where the control panel is not loading for some customers.\n\nOur technicians are aware of the problem and are actively working to identify the root cause and implement a solution as quickly as possible.\n\nWe will provide further updates as more information becomes available.\n\nThank you for your patience.",
206
  "first_seen": "2026-09-04T07:06:16Z",
207
  "impact": "none",
208
+ "last_seen": "2026-09-04T14:19:03Z",
209
  "resolved_at": "2026-04-20T09:30:00.000+02:00",
210
  "resolved_inferred": false,
211
  "started_at": "2026-04-20T09:30:00.000+02:00",
 
218
  "body": "Resolved\nWebmail access has now been fully restored, and all systems are verified to be working as expected again.\n\nIf you are still having problems accessing related services with us, please get in touch with us on chat or email here: https://www.one.com/chat.\nPosted Feb 13, 2026 - 17:11 CET\n\nMonitoring\nA fix has been implemented, and the issue seems to be resolved. \n\nWe are currently monitoring the situation to ensure continued stability.\nPosted Feb 13, 2026 - 16:04 CET\n\nIdentified\nThe prevoius issue with webmail has reappeared, we are working on fixing it in a different way\nPosted Feb 13, 2026 - 14:50 CET\n\nMonitoring\nA fix has been implemented, and we will monitor the situation for a while.\nPosted Feb 13, 2026 - 14:26 CET\n\nIdentified\nThe issue has been identifed, and a fix is being worked on as we speak.\nPosted Feb 13, 2026 - 13:38 CET\n\nInvestigating\nWe are currently investigating an issue affecting our webmail service.\n\nA further update will be provided no later than 13:45 CET",
219
  "first_seen": "2026-09-04T07:06:16Z",
220
  "impact": "none",
221
+ "last_seen": "2026-09-04T14:19:03Z",
222
  "resolved_at": "2026-02-13T13:14:00.000+01:00",
223
  "resolved_inferred": false,
224
  "started_at": "2026-02-13T13:14:00.000+01:00",
api/v/oneschema.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "oneschema",
4
  "platform": "statuspage",
5
  "status_url": "https://status.oneschema.co",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "none",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-07-28T20:30:51.242Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-07-28T19:21:36.965Z",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-07-17T21:29:37.251Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-07-17T21:05:57.000Z",
@@ -38,7 +38,7 @@
38
  "body": "An infrastructure change caused unhealthy nodes that led to imports failing in US production.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "major",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-05-05T00:30:00.000Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-05-05T00:30:00.000Z",
@@ -51,7 +51,7 @@
51
  "body": "We had a temporary outage of our web services that lasted about 5 minutes, starting at 9:40 am PT. All services are back online now and we're monitoring the situation.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "none",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-02-10T17:40:00.000Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-02-10T17:40:00.000Z",
@@ -64,7 +64,7 @@
64
  "body": "Service is stable, incident is resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-01-12T20:23:05.969Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-01-12T20:05:38.672Z",
@@ -77,7 +77,7 @@
77
  "body": "All systems are back to normal performance now.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2025-09-30T02:40:05.105Z",
82
  "resolved_inferred": false,
83
  "started_at": "2025-09-29T16:04:40.033Z",
@@ -90,7 +90,7 @@
90
  "body": "OneSchema has experienced an partial outage on the US server. Total downtime was 23 minutes from 11:45am to 12:08pm PT. An unintentional infrastructure change caused this outage and a fix has been implemented to resolve the issue and prevent it from happening again in the future.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "major",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2025-08-06T19:00:00.000Z",
95
  "resolved_inferred": false,
96
  "started_at": "2025-08-06T19:00:00.000Z",
 
3
  "slug": "oneschema",
4
  "platform": "statuspage",
5
  "status_url": "https://status.oneschema.co",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "none",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-07-28T20:30:51.242Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-07-28T19:21:36.965Z",
 
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-07-17T21:29:37.251Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-07-17T21:05:57.000Z",
 
38
  "body": "An infrastructure change caused unhealthy nodes that led to imports failing in US production.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "major",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-05-05T00:30:00.000Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-05-05T00:30:00.000Z",
 
51
  "body": "We had a temporary outage of our web services that lasted about 5 minutes, starting at 9:40 am PT. All services are back online now and we're monitoring the situation.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "none",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-02-10T17:40:00.000Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-02-10T17:40:00.000Z",
 
64
  "body": "Service is stable, incident is resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-01-12T20:23:05.969Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-01-12T20:05:38.672Z",
 
77
  "body": "All systems are back to normal performance now.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2025-09-30T02:40:05.105Z",
82
  "resolved_inferred": false,
83
  "started_at": "2025-09-29T16:04:40.033Z",
 
90
  "body": "OneSchema has experienced an partial outage on the US server. Total downtime was 23 minutes from 11:45am to 12:08pm PT. An unintentional infrastructure change caused this outage and a fix has been implemented to resolve the issue and prevent it from happening again in the future.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "major",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2025-08-06T19:00:00.000Z",
95
  "resolved_inferred": false,
96
  "started_at": "2025-08-06T19:00:00.000Z",
api/v/openai.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "openai",
4
  "platform": "statuspage",
5
  "status_url": "https://status.openai.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "All impacted services have now fully recovered.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-09-04T10:46:54Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-04T07:00:26Z",
@@ -24,7 +24,7 @@
24
  "body": "The issue causing elevated errors across ChatGPT and Codex has been resolved.\n\nSome Codex remote control users may need to pair their mobile device again following this incident.",
25
  "first_seen": "2026-09-04T07:06:16Z",
26
  "impact": "minor",
27
- "last_seen": "2026-09-04T12:24:18Z",
28
  "resolved_at": "2026-09-03T16:55:49Z",
29
  "resolved_inferred": false,
30
  "started_at": "2026-09-03T14:58:23Z",
@@ -36,7 +36,7 @@
36
  "body": "All impacted services have now fully recovered.",
37
  "first_seen": "2026-09-04T07:06:16Z",
38
  "impact": "major",
39
- "last_seen": "2026-09-04T12:24:18Z",
40
  "resolved_at": "2026-09-03T00:10:45Z",
41
  "resolved_inferred": false,
42
  "started_at": "2026-09-03T00:04:23Z",
@@ -48,7 +48,7 @@
48
  "body": "The issue affecting new account creation has been resolved.",
49
  "first_seen": "2026-09-04T07:06:16Z",
50
  "impact": "none",
51
- "last_seen": "2026-09-04T12:24:18Z",
52
  "resolved_at": "2026-09-02T18:45:12Z",
53
  "resolved_inferred": false,
54
  "started_at": "2026-09-02T18:13:48Z",
@@ -60,7 +60,7 @@
60
  "body": "All impacted services have now fully recovered.",
61
  "first_seen": "2026-09-04T07:06:16Z",
62
  "impact": "minor",
63
- "last_seen": "2026-09-04T12:24:18Z",
64
  "resolved_at": "2026-09-01T01:00:01Z",
65
  "resolved_inferred": false,
66
  "started_at": "2026-09-01T00:38:15Z",
@@ -72,7 +72,7 @@
72
  "body": "All impacted services have now fully recovered.",
73
  "first_seen": "2026-09-04T07:06:16Z",
74
  "impact": "minor",
75
- "last_seen": "2026-09-04T12:24:18Z",
76
  "resolved_at": "2026-09-01T19:05:46Z",
77
  "resolved_inferred": false,
78
  "started_at": "2026-08-31T22:27:56Z",
@@ -84,7 +84,7 @@
84
  "body": "All impacted services have now fully recovered.",
85
  "first_seen": "2026-09-04T07:06:16Z",
86
  "impact": "major",
87
- "last_seen": "2026-09-04T12:24:18Z",
88
  "resolved_at": "2026-08-31T20:28:40Z",
89
  "resolved_inferred": false,
90
  "started_at": "2026-08-31T15:04:53Z",
@@ -96,7 +96,7 @@
96
  "body": "All impacted services have now fully recovered.",
97
  "first_seen": "2026-09-04T07:06:16Z",
98
  "impact": "minor",
99
- "last_seen": "2026-09-04T12:24:18Z",
100
  "resolved_at": "2026-08-27T22:14:44Z",
101
  "resolved_inferred": false,
102
  "started_at": "2026-08-27T18:00:38Z",
@@ -108,7 +108,7 @@
108
  "body": "The issue causing some ChatGPT web users to be unexpectedly logged out when refreshing the page has been resolved.",
109
  "first_seen": "2026-09-04T07:06:16Z",
110
  "impact": "minor",
111
- "last_seen": "2026-09-04T12:24:18Z",
112
  "resolved_at": "2026-08-21T23:15:09Z",
113
  "resolved_inferred": false,
114
  "started_at": "2026-08-21T19:48:34Z",
@@ -120,7 +120,7 @@
120
  "body": "All impacted services have now fully recovered.",
121
  "first_seen": "2026-09-04T07:06:16Z",
122
  "impact": "minor",
123
- "last_seen": "2026-09-04T12:24:18Z",
124
  "resolved_at": "2026-08-20T17:52:16Z",
125
  "resolved_inferred": false,
126
  "started_at": "2026-08-20T16:58:53Z",
@@ -132,7 +132,7 @@
132
  "body": "All impacted services have now fully recovered.",
133
  "first_seen": "2026-09-04T07:06:16Z",
134
  "impact": "minor",
135
- "last_seen": "2026-09-04T12:24:18Z",
136
  "resolved_at": "2026-08-20T16:51:51Z",
137
  "resolved_inferred": false,
138
  "started_at": "2026-08-20T13:56:21Z",
@@ -144,7 +144,7 @@
144
  "body": "All impacted services have now fully recovered.",
145
  "first_seen": "2026-09-04T07:06:16Z",
146
  "impact": "minor",
147
- "last_seen": "2026-09-04T12:24:18Z",
148
  "resolved_at": "2026-08-20T00:54:17Z",
149
  "resolved_inferred": false,
150
  "started_at": "2026-08-20T00:02:08Z",
@@ -156,7 +156,7 @@
156
  "body": "The issue affecting site deployments has been resolved.",
157
  "first_seen": "2026-09-04T07:06:16Z",
158
  "impact": "minor",
159
- "last_seen": "2026-09-04T12:24:18Z",
160
  "resolved_at": "2026-08-18T19:37:24Z",
161
  "resolved_inferred": false,
162
  "started_at": "2026-08-18T19:17:12Z",
@@ -168,7 +168,7 @@
168
  "body": "All impacted services have now fully recovered.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "minor",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2026-08-13T23:58:22Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-08-13T15:19:50Z",
@@ -180,7 +180,7 @@
180
  "body": "All impacted services have now fully recovered.",
181
  "first_seen": "2026-09-04T07:06:16Z",
182
  "impact": "none",
183
- "last_seen": "2026-09-04T12:24:18Z",
184
  "resolved_at": "2026-08-13T22:26:53Z",
185
  "resolved_inferred": false,
186
  "started_at": "2026-08-13T14:03:49Z",
@@ -192,7 +192,7 @@
192
  "body": "All impacted services have now fully recovered.",
193
  "first_seen": "2026-09-04T07:06:16Z",
194
  "impact": "none",
195
- "last_seen": "2026-09-04T12:24:18Z",
196
  "resolved_at": "2026-08-11T22:42:26Z",
197
  "resolved_inferred": false,
198
  "started_at": "2026-08-11T21:35:23Z",
@@ -204,7 +204,7 @@
204
  "body": "All impacted services have now fully recovered.",
205
  "first_seen": "2026-09-04T07:06:16Z",
206
  "impact": "minor",
207
- "last_seen": "2026-09-04T12:24:18Z",
208
  "resolved_at": "2026-08-11T17:28:04Z",
209
  "resolved_inferred": false,
210
  "started_at": "2026-08-11T17:25:03Z",
@@ -216,7 +216,7 @@
216
  "body": "All impacted services have now fully recovered.",
217
  "first_seen": "2026-09-04T07:06:16Z",
218
  "impact": "minor",
219
- "last_seen": "2026-09-04T12:24:18Z",
220
  "resolved_at": "2026-08-11T14:20:28Z",
221
  "resolved_inferred": false,
222
  "started_at": "2026-08-11T14:10:18Z",
@@ -228,7 +228,7 @@
228
  "body": "All impacted services have now fully recovered.",
229
  "first_seen": "2026-09-04T07:06:16Z",
230
  "impact": "minor",
231
- "last_seen": "2026-09-04T12:24:18Z",
232
  "resolved_at": "2026-08-11T15:01:38Z",
233
  "resolved_inferred": false,
234
  "started_at": "2026-08-11T12:54:28Z",
@@ -240,7 +240,7 @@
240
  "body": "All impacted services have now fully recovered.",
241
  "first_seen": "2026-09-04T07:06:16Z",
242
  "impact": "minor",
243
- "last_seen": "2026-09-04T12:24:18Z",
244
  "resolved_at": "2026-08-11T02:48:20Z",
245
  "resolved_inferred": false,
246
  "started_at": "2026-08-10T14:04:37Z",
@@ -252,7 +252,7 @@
252
  "body": "All impacted services have now fully recovered.",
253
  "first_seen": "2026-09-04T07:06:16Z",
254
  "impact": "minor",
255
- "last_seen": "2026-09-04T12:24:18Z",
256
  "resolved_at": "2026-08-10T08:09:19Z",
257
  "resolved_inferred": false,
258
  "started_at": "2026-08-10T07:21:42Z",
@@ -264,7 +264,7 @@
264
  "body": "All impacted services have now fully recovered.",
265
  "first_seen": "2026-09-04T07:06:16Z",
266
  "impact": "minor",
267
- "last_seen": "2026-09-04T12:24:18Z",
268
  "resolved_at": "2026-08-05T20:19:28Z",
269
  "resolved_inferred": false,
270
  "started_at": "2026-08-05T17:06:16Z",
@@ -276,7 +276,7 @@
276
  "body": "All impacted services have now fully recovered.",
277
  "first_seen": "2026-09-04T07:06:16Z",
278
  "impact": "minor",
279
- "last_seen": "2026-09-04T12:24:18Z",
280
  "resolved_at": "2026-08-05T22:49:08Z",
281
  "resolved_inferred": false,
282
  "started_at": "2026-08-05T16:55:54Z",
@@ -288,7 +288,7 @@
288
  "body": "All impacted services have now fully recovered.",
289
  "first_seen": "2026-09-04T07:06:16Z",
290
  "impact": "minor",
291
- "last_seen": "2026-09-04T12:24:18Z",
292
  "resolved_at": "2026-08-05T23:22:45Z",
293
  "resolved_inferred": false,
294
  "started_at": "2026-08-05T14:55:59Z",
@@ -300,7 +300,7 @@
300
  "body": "All impacted services have now fully recovered.",
301
  "first_seen": "2026-09-04T07:06:16Z",
302
  "impact": "minor",
303
- "last_seen": "2026-09-04T12:24:18Z",
304
  "resolved_at": "2026-08-04T15:25:30Z",
305
  "resolved_inferred": false,
306
  "started_at": "2026-08-04T12:43:44Z",
 
3
  "slug": "openai",
4
  "platform": "statuspage",
5
  "status_url": "https://status.openai.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "All impacted services have now fully recovered.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-09-04T10:46:54Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-04T07:00:26Z",
 
24
  "body": "The issue causing elevated errors across ChatGPT and Codex has been resolved.\n\nSome Codex remote control users may need to pair their mobile device again following this incident.",
25
  "first_seen": "2026-09-04T07:06:16Z",
26
  "impact": "minor",
27
+ "last_seen": "2026-09-04T14:19:03Z",
28
  "resolved_at": "2026-09-03T16:55:49Z",
29
  "resolved_inferred": false,
30
  "started_at": "2026-09-03T14:58:23Z",
 
36
  "body": "All impacted services have now fully recovered.",
37
  "first_seen": "2026-09-04T07:06:16Z",
38
  "impact": "major",
39
+ "last_seen": "2026-09-04T14:19:03Z",
40
  "resolved_at": "2026-09-03T00:10:45Z",
41
  "resolved_inferred": false,
42
  "started_at": "2026-09-03T00:04:23Z",
 
48
  "body": "The issue affecting new account creation has been resolved.",
49
  "first_seen": "2026-09-04T07:06:16Z",
50
  "impact": "none",
51
+ "last_seen": "2026-09-04T14:19:03Z",
52
  "resolved_at": "2026-09-02T18:45:12Z",
53
  "resolved_inferred": false,
54
  "started_at": "2026-09-02T18:13:48Z",
 
60
  "body": "All impacted services have now fully recovered.",
61
  "first_seen": "2026-09-04T07:06:16Z",
62
  "impact": "minor",
63
+ "last_seen": "2026-09-04T14:19:03Z",
64
  "resolved_at": "2026-09-01T01:00:01Z",
65
  "resolved_inferred": false,
66
  "started_at": "2026-09-01T00:38:15Z",
 
72
  "body": "All impacted services have now fully recovered.",
73
  "first_seen": "2026-09-04T07:06:16Z",
74
  "impact": "minor",
75
+ "last_seen": "2026-09-04T14:19:03Z",
76
  "resolved_at": "2026-09-01T19:05:46Z",
77
  "resolved_inferred": false,
78
  "started_at": "2026-08-31T22:27:56Z",
 
84
  "body": "All impacted services have now fully recovered.",
85
  "first_seen": "2026-09-04T07:06:16Z",
86
  "impact": "major",
87
+ "last_seen": "2026-09-04T14:19:03Z",
88
  "resolved_at": "2026-08-31T20:28:40Z",
89
  "resolved_inferred": false,
90
  "started_at": "2026-08-31T15:04:53Z",
 
96
  "body": "All impacted services have now fully recovered.",
97
  "first_seen": "2026-09-04T07:06:16Z",
98
  "impact": "minor",
99
+ "last_seen": "2026-09-04T14:19:03Z",
100
  "resolved_at": "2026-08-27T22:14:44Z",
101
  "resolved_inferred": false,
102
  "started_at": "2026-08-27T18:00:38Z",
 
108
  "body": "The issue causing some ChatGPT web users to be unexpectedly logged out when refreshing the page has been resolved.",
109
  "first_seen": "2026-09-04T07:06:16Z",
110
  "impact": "minor",
111
+ "last_seen": "2026-09-04T14:19:03Z",
112
  "resolved_at": "2026-08-21T23:15:09Z",
113
  "resolved_inferred": false,
114
  "started_at": "2026-08-21T19:48:34Z",
 
120
  "body": "All impacted services have now fully recovered.",
121
  "first_seen": "2026-09-04T07:06:16Z",
122
  "impact": "minor",
123
+ "last_seen": "2026-09-04T14:19:03Z",
124
  "resolved_at": "2026-08-20T17:52:16Z",
125
  "resolved_inferred": false,
126
  "started_at": "2026-08-20T16:58:53Z",
 
132
  "body": "All impacted services have now fully recovered.",
133
  "first_seen": "2026-09-04T07:06:16Z",
134
  "impact": "minor",
135
+ "last_seen": "2026-09-04T14:19:03Z",
136
  "resolved_at": "2026-08-20T16:51:51Z",
137
  "resolved_inferred": false,
138
  "started_at": "2026-08-20T13:56:21Z",
 
144
  "body": "All impacted services have now fully recovered.",
145
  "first_seen": "2026-09-04T07:06:16Z",
146
  "impact": "minor",
147
+ "last_seen": "2026-09-04T14:19:03Z",
148
  "resolved_at": "2026-08-20T00:54:17Z",
149
  "resolved_inferred": false,
150
  "started_at": "2026-08-20T00:02:08Z",
 
156
  "body": "The issue affecting site deployments has been resolved.",
157
  "first_seen": "2026-09-04T07:06:16Z",
158
  "impact": "minor",
159
+ "last_seen": "2026-09-04T14:19:03Z",
160
  "resolved_at": "2026-08-18T19:37:24Z",
161
  "resolved_inferred": false,
162
  "started_at": "2026-08-18T19:17:12Z",
 
168
  "body": "All impacted services have now fully recovered.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "minor",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2026-08-13T23:58:22Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-08-13T15:19:50Z",
 
180
  "body": "All impacted services have now fully recovered.",
181
  "first_seen": "2026-09-04T07:06:16Z",
182
  "impact": "none",
183
+ "last_seen": "2026-09-04T14:19:03Z",
184
  "resolved_at": "2026-08-13T22:26:53Z",
185
  "resolved_inferred": false,
186
  "started_at": "2026-08-13T14:03:49Z",
 
192
  "body": "All impacted services have now fully recovered.",
193
  "first_seen": "2026-09-04T07:06:16Z",
194
  "impact": "none",
195
+ "last_seen": "2026-09-04T14:19:03Z",
196
  "resolved_at": "2026-08-11T22:42:26Z",
197
  "resolved_inferred": false,
198
  "started_at": "2026-08-11T21:35:23Z",
 
204
  "body": "All impacted services have now fully recovered.",
205
  "first_seen": "2026-09-04T07:06:16Z",
206
  "impact": "minor",
207
+ "last_seen": "2026-09-04T14:19:03Z",
208
  "resolved_at": "2026-08-11T17:28:04Z",
209
  "resolved_inferred": false,
210
  "started_at": "2026-08-11T17:25:03Z",
 
216
  "body": "All impacted services have now fully recovered.",
217
  "first_seen": "2026-09-04T07:06:16Z",
218
  "impact": "minor",
219
+ "last_seen": "2026-09-04T14:19:03Z",
220
  "resolved_at": "2026-08-11T14:20:28Z",
221
  "resolved_inferred": false,
222
  "started_at": "2026-08-11T14:10:18Z",
 
228
  "body": "All impacted services have now fully recovered.",
229
  "first_seen": "2026-09-04T07:06:16Z",
230
  "impact": "minor",
231
+ "last_seen": "2026-09-04T14:19:03Z",
232
  "resolved_at": "2026-08-11T15:01:38Z",
233
  "resolved_inferred": false,
234
  "started_at": "2026-08-11T12:54:28Z",
 
240
  "body": "All impacted services have now fully recovered.",
241
  "first_seen": "2026-09-04T07:06:16Z",
242
  "impact": "minor",
243
+ "last_seen": "2026-09-04T14:19:03Z",
244
  "resolved_at": "2026-08-11T02:48:20Z",
245
  "resolved_inferred": false,
246
  "started_at": "2026-08-10T14:04:37Z",
 
252
  "body": "All impacted services have now fully recovered.",
253
  "first_seen": "2026-09-04T07:06:16Z",
254
  "impact": "minor",
255
+ "last_seen": "2026-09-04T14:19:03Z",
256
  "resolved_at": "2026-08-10T08:09:19Z",
257
  "resolved_inferred": false,
258
  "started_at": "2026-08-10T07:21:42Z",
 
264
  "body": "All impacted services have now fully recovered.",
265
  "first_seen": "2026-09-04T07:06:16Z",
266
  "impact": "minor",
267
+ "last_seen": "2026-09-04T14:19:03Z",
268
  "resolved_at": "2026-08-05T20:19:28Z",
269
  "resolved_inferred": false,
270
  "started_at": "2026-08-05T17:06:16Z",
 
276
  "body": "All impacted services have now fully recovered.",
277
  "first_seen": "2026-09-04T07:06:16Z",
278
  "impact": "minor",
279
+ "last_seen": "2026-09-04T14:19:03Z",
280
  "resolved_at": "2026-08-05T22:49:08Z",
281
  "resolved_inferred": false,
282
  "started_at": "2026-08-05T16:55:54Z",
 
288
  "body": "All impacted services have now fully recovered.",
289
  "first_seen": "2026-09-04T07:06:16Z",
290
  "impact": "minor",
291
+ "last_seen": "2026-09-04T14:19:03Z",
292
  "resolved_at": "2026-08-05T23:22:45Z",
293
  "resolved_inferred": false,
294
  "started_at": "2026-08-05T14:55:59Z",
 
300
  "body": "All impacted services have now fully recovered.",
301
  "first_seen": "2026-09-04T07:06:16Z",
302
  "impact": "minor",
303
+ "last_seen": "2026-09-04T14:19:03Z",
304
  "resolved_at": "2026-08-04T15:25:30Z",
305
  "resolved_inferred": false,
306
  "started_at": "2026-08-04T12:43:44Z",
api/v/opencage.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "opencage",
4
  "platform": "instatus",
5
  "status_url": "https://status.opencagedata.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": false,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
3
  "slug": "opencage",
4
  "platform": "instatus",
5
  "status_url": "https://status.opencagedata.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": false,
9
  "first_watched": "2026-09-04T07:06:16Z",
api/v/opencorporates.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "opencorporates",
4
  "platform": "betterstack",
5
  "status_url": "https://status.opencorporates.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": false,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
3
  "slug": "opencorporates",
4
  "platform": "betterstack",
5
  "status_url": "https://status.opencorporates.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": false,
9
  "first_watched": "2026-09-04T07:06:16Z",
api/v/opengov-inc.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "opengov-inc",
4
  "platform": "statuspage",
5
  "status_url": "https://www.opengovstatus.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "critical",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-08-26T09:04:38.871-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-26T08:20:28.093-07:00",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved. Vendors submitting responses via DocuSign PowerForms should no longer experience syncing issues.\n\nGoing forward, customers need to create a new Connection in their DocuSign account per this article: \n\nhttps://opengov.my.site.com/support/s/article/ebfdc36e-8f30-4faf-8c9e-fa2205c4e015",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-08-26T07:40:55.690-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-20T08:31:40.474-07:00",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-08-17T13:27:27.176-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-08-17T10:28:29.792-07:00",
@@ -51,7 +51,7 @@
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "critical",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-08-17T10:26:23.619-07:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-08-17T07:16:48.228-07:00",
@@ -64,7 +64,7 @@
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "critical",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-08-13T15:39:05.803-07:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-08-13T14:35:02.085-07:00",
@@ -77,7 +77,7 @@
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "critical",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-08-17T14:12:23.666-07:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-08-13T08:14:30.000-07:00",
@@ -90,7 +90,7 @@
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "major",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-08-11T09:38:53.149-07:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-08-11T08:19:04.781-07:00",
@@ -103,7 +103,7 @@
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "major",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-07-31T13:55:14.198-07:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-07-31T09:14:28.682-07:00",
@@ -116,7 +116,7 @@
116
  "body": "This incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-07-28T09:01:51.806-07:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-07-28T07:44:47.626-07:00",
@@ -129,7 +129,7 @@
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "major",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-07-23T07:11:11.710-07:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-07-23T05:01:01.127-07:00",
@@ -142,7 +142,7 @@
142
  "body": "This incident has been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "major",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2026-07-14T06:09:43.754-07:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-07-13T13:11:45.310-07:00",
@@ -155,7 +155,7 @@
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "critical",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2026-07-10T12:54:40.393-07:00",
160
  "resolved_inferred": false,
161
  "started_at": "2026-07-10T10:13:20.655-07:00",
@@ -168,7 +168,7 @@
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2026-06-27T06:55:54.535-07:00",
173
  "resolved_inferred": false,
174
  "started_at": "2026-06-26T11:32:47.898-07:00",
@@ -181,7 +181,7 @@
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "none",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2026-06-26T05:06:06.312-07:00",
186
  "resolved_inferred": false,
187
  "started_at": "2026-06-25T09:44:48.979-07:00",
@@ -194,7 +194,7 @@
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "critical",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2026-06-23T08:22:43.082-07:00",
199
  "resolved_inferred": false,
200
  "started_at": "2026-06-23T07:50:36.806-07:00",
@@ -207,7 +207,7 @@
207
  "body": "This incident has been resolved.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "major",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2026-06-22T08:17:55.917-07:00",
212
  "resolved_inferred": false,
213
  "started_at": "2026-06-22T07:01:14.444-07:00",
@@ -220,7 +220,7 @@
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "major",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2026-06-16T07:35:51.454-07:00",
225
  "resolved_inferred": false,
226
  "started_at": "2026-06-15T07:20:26.034-07:00",
@@ -233,7 +233,7 @@
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "minor",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2026-06-11T13:28:43.116-07:00",
238
  "resolved_inferred": false,
239
  "started_at": "2026-06-11T13:09:30.149-07:00",
@@ -246,7 +246,7 @@
246
  "body": "This incident has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "minor",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2026-06-15T06:36:03.459-07:00",
251
  "resolved_inferred": false,
252
  "started_at": "2026-06-11T10:44:48.799-07:00",
@@ -259,7 +259,7 @@
259
  "body": "This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "critical",
262
- "last_seen": "2026-09-04T12:24:18Z",
263
  "resolved_at": "2026-06-08T05:48:53.486-07:00",
264
  "resolved_inferred": false,
265
  "started_at": "2026-06-08T04:03:52.024-07:00",
@@ -272,7 +272,7 @@
272
  "body": "This incident has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "none",
275
- "last_seen": "2026-09-04T12:24:18Z",
276
  "resolved_at": "2026-06-01T07:37:34.609-07:00",
277
  "resolved_inferred": false,
278
  "started_at": "2026-06-01T06:42:23.714-07:00",
@@ -285,7 +285,7 @@
285
  "body": "This incident has been resolved.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "critical",
288
- "last_seen": "2026-09-04T12:24:18Z",
289
  "resolved_at": "2026-05-26T07:04:50.786-07:00",
290
  "resolved_inferred": false,
291
  "started_at": "2026-05-26T06:26:37.522-07:00",
@@ -298,7 +298,7 @@
298
  "body": "This incident has been resolved.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "major",
301
- "last_seen": "2026-09-04T12:24:18Z",
302
  "resolved_at": "2026-05-28T04:25:48.295-07:00",
303
  "resolved_inferred": false,
304
  "started_at": "2026-05-21T07:26:01.256-07:00",
@@ -311,7 +311,7 @@
311
  "body": "This incident has been resolved.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "major",
314
- "last_seen": "2026-09-04T12:24:18Z",
315
  "resolved_at": "2026-05-22T11:59:36.375-07:00",
316
  "resolved_inferred": false,
317
  "started_at": "2026-05-20T10:39:07.458-07:00",
@@ -324,7 +324,7 @@
324
  "body": "This incident has been resolved.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "minor",
327
- "last_seen": "2026-09-04T12:24:18Z",
328
  "resolved_at": "2026-05-20T10:09:33.324-07:00",
329
  "resolved_inferred": false,
330
  "started_at": "2026-05-20T09:11:39.166-07:00",
@@ -337,7 +337,7 @@
337
  "body": "This incident has been resolved. Data remediation will be completed to revert the most recent Penalties & Interest run. Re-running the Penalties & Interest process, should correct any affected charges.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "minor",
340
- "last_seen": "2026-09-04T12:24:18Z",
341
  "resolved_at": "2026-05-13T05:46:56.201-07:00",
342
  "resolved_inferred": false,
343
  "started_at": "2026-05-05T11:19:51.312-07:00",
@@ -350,7 +350,7 @@
350
  "body": "This incident has been resolved.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "minor",
353
- "last_seen": "2026-09-04T12:24:18Z",
354
  "resolved_at": "2026-05-04T11:52:08.880-07:00",
355
  "resolved_inferred": false,
356
  "started_at": "2026-05-04T09:42:56.489-07:00",
@@ -363,7 +363,7 @@
363
  "body": "This incident has been resolved.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "minor",
366
- "last_seen": "2026-09-04T12:24:18Z",
367
  "resolved_at": "2026-05-13T05:45:33.843-07:00",
368
  "resolved_inferred": false,
369
  "started_at": "2026-05-04T08:24:00.148-07:00",
@@ -376,7 +376,7 @@
376
  "body": "This incident has been resolved.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "major",
379
- "last_seen": "2026-09-04T12:24:18Z",
380
  "resolved_at": "2026-04-24T16:12:58.669-07:00",
381
  "resolved_inferred": false,
382
  "started_at": "2026-04-24T06:44:30.159-07:00",
@@ -389,7 +389,7 @@
389
  "body": "This incident has been resolved.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "critical",
392
- "last_seen": "2026-09-04T12:24:18Z",
393
  "resolved_at": "2026-04-24T13:18:55.503-07:00",
394
  "resolved_inferred": false,
395
  "started_at": "2026-04-21T13:40:21.105-07:00",
@@ -402,7 +402,7 @@
402
  "body": "This incident has been resolved.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "minor",
405
- "last_seen": "2026-09-04T12:24:18Z",
406
  "resolved_at": "2026-04-21T13:47:32.291-07:00",
407
  "resolved_inferred": false,
408
  "started_at": "2026-04-21T10:24:28.813-07:00",
@@ -415,7 +415,7 @@
415
  "body": "This incident has been resolved.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "minor",
418
- "last_seen": "2026-09-04T12:24:18Z",
419
  "resolved_at": "2026-04-20T12:06:08.090-07:00",
420
  "resolved_inferred": false,
421
  "started_at": "2026-04-20T09:00:01.381-07:00",
@@ -428,7 +428,7 @@
428
  "body": "This incident has been resolved.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "major",
431
- "last_seen": "2026-09-04T12:24:18Z",
432
  "resolved_at": "2026-04-15T15:22:21.375-07:00",
433
  "resolved_inferred": false,
434
  "started_at": "2026-04-15T06:05:44.000-07:00",
@@ -441,7 +441,7 @@
441
  "body": "This incident has been resolved.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "major",
444
- "last_seen": "2026-09-04T12:24:18Z",
445
  "resolved_at": "2026-04-13T13:45:57.496-07:00",
446
  "resolved_inferred": false,
447
  "started_at": "2026-04-13T12:27:46.882-07:00",
@@ -454,7 +454,7 @@
454
  "body": "This incident has been resolved.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "major",
457
- "last_seen": "2026-09-04T12:24:18Z",
458
  "resolved_at": "2026-04-07T14:30:01.440-07:00",
459
  "resolved_inferred": false,
460
  "started_at": "2026-04-07T11:33:40.779-07:00",
@@ -467,7 +467,7 @@
467
  "body": "This incident has been resolved.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "major",
470
- "last_seen": "2026-09-04T12:24:18Z",
471
  "resolved_at": "2026-04-06T13:04:36.164-07:00",
472
  "resolved_inferred": false,
473
  "started_at": "2026-04-06T11:36:19.790-07:00",
@@ -480,7 +480,7 @@
480
  "body": "This incident has been resolved.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "minor",
483
- "last_seen": "2026-09-04T12:24:18Z",
484
  "resolved_at": "2026-04-06T11:35:46.595-07:00",
485
  "resolved_inferred": false,
486
  "started_at": "2026-03-31T11:51:23.000-07:00",
@@ -493,7 +493,7 @@
493
  "body": "This incident has been resolved.",
494
  "first_seen": "2026-09-04T07:06:16Z",
495
  "impact": "major",
496
- "last_seen": "2026-09-04T12:24:18Z",
497
  "resolved_at": "2026-04-01T07:42:59.127-07:00",
498
  "resolved_inferred": false,
499
  "started_at": "2026-03-31T08:17:40.053-07:00",
@@ -506,7 +506,7 @@
506
  "body": "This incident has been resolved.",
507
  "first_seen": "2026-09-04T07:06:16Z",
508
  "impact": "none",
509
- "last_seen": "2026-09-04T12:24:18Z",
510
  "resolved_at": "2026-03-27T09:29:47.155-07:00",
511
  "resolved_inferred": false,
512
  "started_at": "2026-03-26T12:32:24.804-07:00",
@@ -519,7 +519,7 @@
519
  "body": "This incident has been resolved.",
520
  "first_seen": "2026-09-04T07:06:16Z",
521
  "impact": "none",
522
- "last_seen": "2026-09-04T12:24:18Z",
523
  "resolved_at": "2026-03-27T09:29:37.890-07:00",
524
  "resolved_inferred": false,
525
  "started_at": "2026-03-25T14:53:07.102-07:00",
@@ -532,7 +532,7 @@
532
  "body": "The situation has been fully resolved. All sites have been reviewed, and workflows are now progressing as expected. Thank you for your patience.",
533
  "first_seen": "2026-09-04T07:06:16Z",
534
  "impact": "minor",
535
- "last_seen": "2026-09-04T12:24:18Z",
536
  "resolved_at": "2026-03-27T08:03:37.793-07:00",
537
  "resolved_inferred": false,
538
  "started_at": "2026-03-25T08:38:40.636-07:00",
@@ -545,7 +545,7 @@
545
  "body": "This incident has been resolved.",
546
  "first_seen": "2026-09-04T07:06:16Z",
547
  "impact": "minor",
548
- "last_seen": "2026-09-04T12:24:18Z",
549
  "resolved_at": "2026-03-24T07:53:53.619-07:00",
550
  "resolved_inferred": false,
551
  "started_at": "2026-03-24T05:57:05.584-07:00",
@@ -558,7 +558,7 @@
558
  "body": "This incident has been resolved.",
559
  "first_seen": "2026-09-04T07:06:16Z",
560
  "impact": "minor",
561
- "last_seen": "2026-09-04T12:24:18Z",
562
  "resolved_at": "2026-03-24T05:28:50.578-07:00",
563
  "resolved_inferred": false,
564
  "started_at": "2026-03-23T05:18:37.562-07:00",
@@ -571,7 +571,7 @@
571
  "body": "This incident has been resolved.",
572
  "first_seen": "2026-09-04T07:06:16Z",
573
  "impact": "none",
574
- "last_seen": "2026-09-04T12:24:18Z",
575
  "resolved_at": "2026-03-18T05:10:11.644-07:00",
576
  "resolved_inferred": false,
577
  "started_at": "2026-03-17T10:31:34.680-07:00",
@@ -584,7 +584,7 @@
584
  "body": "This incident has been resolved.",
585
  "first_seen": "2026-09-04T07:06:16Z",
586
  "impact": "critical",
587
- "last_seen": "2026-09-04T12:24:18Z",
588
  "resolved_at": "2026-03-16T14:43:45.439-07:00",
589
  "resolved_inferred": false,
590
  "started_at": "2026-03-16T09:51:03.119-07:00",
@@ -597,7 +597,7 @@
597
  "body": "This incident has been resolved.",
598
  "first_seen": "2026-09-04T07:06:16Z",
599
  "impact": "none",
600
- "last_seen": "2026-09-04T12:24:18Z",
601
  "resolved_at": "2026-03-13T18:27:11.546-07:00",
602
  "resolved_inferred": false,
603
  "started_at": "2026-03-13T13:49:44.599-07:00",
@@ -610,7 +610,7 @@
610
  "body": "This incident has been resolved.",
611
  "first_seen": "2026-09-04T07:06:16Z",
612
  "impact": "minor",
613
- "last_seen": "2026-09-04T12:24:18Z",
614
  "resolved_at": "2026-03-13T04:50:34.426-07:00",
615
  "resolved_inferred": false,
616
  "started_at": "2026-03-12T12:04:08.179-07:00",
@@ -623,7 +623,7 @@
623
  "body": "This incident has been resolved.",
624
  "first_seen": "2026-09-04T07:06:16Z",
625
  "impact": "minor",
626
- "last_seen": "2026-09-04T12:24:18Z",
627
  "resolved_at": "2026-03-04T15:31:55.711-08:00",
628
  "resolved_inferred": false,
629
  "started_at": "2026-03-04T06:24:55.102-08:00",
@@ -636,7 +636,7 @@
636
  "body": "This incident has been resolved.",
637
  "first_seen": "2026-09-04T07:06:16Z",
638
  "impact": "none",
639
- "last_seen": "2026-09-04T12:24:18Z",
640
  "resolved_at": "2026-03-03T12:01:47.776-08:00",
641
  "resolved_inferred": false,
642
  "started_at": "2026-03-02T09:55:11.500-08:00",
@@ -649,7 +649,7 @@
649
  "body": "This incident has been resolved.",
650
  "first_seen": "2026-09-04T07:06:16Z",
651
  "impact": "none",
652
- "last_seen": "2026-09-04T12:24:18Z",
653
  "resolved_at": "2026-03-09T06:00:53.993-07:00",
654
  "resolved_inferred": false,
655
  "started_at": "2026-02-26T08:34:30.998-08:00",
 
3
  "slug": "opengov-inc",
4
  "platform": "statuspage",
5
  "status_url": "https://www.opengovstatus.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "critical",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-08-26T09:04:38.871-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-26T08:20:28.093-07:00",
 
25
  "body": "This incident has been resolved. Vendors submitting responses via DocuSign PowerForms should no longer experience syncing issues.\n\nGoing forward, customers need to create a new Connection in their DocuSign account per this article: \n\nhttps://opengov.my.site.com/support/s/article/ebfdc36e-8f30-4faf-8c9e-fa2205c4e015",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-08-26T07:40:55.690-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-20T08:31:40.474-07:00",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-08-17T13:27:27.176-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-08-17T10:28:29.792-07:00",
 
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "critical",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-08-17T10:26:23.619-07:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-08-17T07:16:48.228-07:00",
 
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "critical",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-08-13T15:39:05.803-07:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-08-13T14:35:02.085-07:00",
 
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "critical",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-08-17T14:12:23.666-07:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-08-13T08:14:30.000-07:00",
 
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "major",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-08-11T09:38:53.149-07:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-08-11T08:19:04.781-07:00",
 
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "major",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-07-31T13:55:14.198-07:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-07-31T09:14:28.682-07:00",
 
116
  "body": "This incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-07-28T09:01:51.806-07:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-07-28T07:44:47.626-07:00",
 
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "major",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-07-23T07:11:11.710-07:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-07-23T05:01:01.127-07:00",
 
142
  "body": "This incident has been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "major",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2026-07-14T06:09:43.754-07:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-07-13T13:11:45.310-07:00",
 
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "critical",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2026-07-10T12:54:40.393-07:00",
160
  "resolved_inferred": false,
161
  "started_at": "2026-07-10T10:13:20.655-07:00",
 
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2026-06-27T06:55:54.535-07:00",
173
  "resolved_inferred": false,
174
  "started_at": "2026-06-26T11:32:47.898-07:00",
 
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "none",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2026-06-26T05:06:06.312-07:00",
186
  "resolved_inferred": false,
187
  "started_at": "2026-06-25T09:44:48.979-07:00",
 
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "critical",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2026-06-23T08:22:43.082-07:00",
199
  "resolved_inferred": false,
200
  "started_at": "2026-06-23T07:50:36.806-07:00",
 
207
  "body": "This incident has been resolved.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "major",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2026-06-22T08:17:55.917-07:00",
212
  "resolved_inferred": false,
213
  "started_at": "2026-06-22T07:01:14.444-07:00",
 
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "major",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2026-06-16T07:35:51.454-07:00",
225
  "resolved_inferred": false,
226
  "started_at": "2026-06-15T07:20:26.034-07:00",
 
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "minor",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2026-06-11T13:28:43.116-07:00",
238
  "resolved_inferred": false,
239
  "started_at": "2026-06-11T13:09:30.149-07:00",
 
246
  "body": "This incident has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "minor",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2026-06-15T06:36:03.459-07:00",
251
  "resolved_inferred": false,
252
  "started_at": "2026-06-11T10:44:48.799-07:00",
 
259
  "body": "This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "critical",
262
+ "last_seen": "2026-09-04T14:19:03Z",
263
  "resolved_at": "2026-06-08T05:48:53.486-07:00",
264
  "resolved_inferred": false,
265
  "started_at": "2026-06-08T04:03:52.024-07:00",
 
272
  "body": "This incident has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "none",
275
+ "last_seen": "2026-09-04T14:19:03Z",
276
  "resolved_at": "2026-06-01T07:37:34.609-07:00",
277
  "resolved_inferred": false,
278
  "started_at": "2026-06-01T06:42:23.714-07:00",
 
285
  "body": "This incident has been resolved.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "critical",
288
+ "last_seen": "2026-09-04T14:19:03Z",
289
  "resolved_at": "2026-05-26T07:04:50.786-07:00",
290
  "resolved_inferred": false,
291
  "started_at": "2026-05-26T06:26:37.522-07:00",
 
298
  "body": "This incident has been resolved.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "major",
301
+ "last_seen": "2026-09-04T14:19:03Z",
302
  "resolved_at": "2026-05-28T04:25:48.295-07:00",
303
  "resolved_inferred": false,
304
  "started_at": "2026-05-21T07:26:01.256-07:00",
 
311
  "body": "This incident has been resolved.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "major",
314
+ "last_seen": "2026-09-04T14:19:03Z",
315
  "resolved_at": "2026-05-22T11:59:36.375-07:00",
316
  "resolved_inferred": false,
317
  "started_at": "2026-05-20T10:39:07.458-07:00",
 
324
  "body": "This incident has been resolved.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "minor",
327
+ "last_seen": "2026-09-04T14:19:03Z",
328
  "resolved_at": "2026-05-20T10:09:33.324-07:00",
329
  "resolved_inferred": false,
330
  "started_at": "2026-05-20T09:11:39.166-07:00",
 
337
  "body": "This incident has been resolved. Data remediation will be completed to revert the most recent Penalties & Interest run. Re-running the Penalties & Interest process, should correct any affected charges.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "minor",
340
+ "last_seen": "2026-09-04T14:19:03Z",
341
  "resolved_at": "2026-05-13T05:46:56.201-07:00",
342
  "resolved_inferred": false,
343
  "started_at": "2026-05-05T11:19:51.312-07:00",
 
350
  "body": "This incident has been resolved.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "minor",
353
+ "last_seen": "2026-09-04T14:19:03Z",
354
  "resolved_at": "2026-05-04T11:52:08.880-07:00",
355
  "resolved_inferred": false,
356
  "started_at": "2026-05-04T09:42:56.489-07:00",
 
363
  "body": "This incident has been resolved.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "minor",
366
+ "last_seen": "2026-09-04T14:19:03Z",
367
  "resolved_at": "2026-05-13T05:45:33.843-07:00",
368
  "resolved_inferred": false,
369
  "started_at": "2026-05-04T08:24:00.148-07:00",
 
376
  "body": "This incident has been resolved.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "major",
379
+ "last_seen": "2026-09-04T14:19:03Z",
380
  "resolved_at": "2026-04-24T16:12:58.669-07:00",
381
  "resolved_inferred": false,
382
  "started_at": "2026-04-24T06:44:30.159-07:00",
 
389
  "body": "This incident has been resolved.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "critical",
392
+ "last_seen": "2026-09-04T14:19:03Z",
393
  "resolved_at": "2026-04-24T13:18:55.503-07:00",
394
  "resolved_inferred": false,
395
  "started_at": "2026-04-21T13:40:21.105-07:00",
 
402
  "body": "This incident has been resolved.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "minor",
405
+ "last_seen": "2026-09-04T14:19:03Z",
406
  "resolved_at": "2026-04-21T13:47:32.291-07:00",
407
  "resolved_inferred": false,
408
  "started_at": "2026-04-21T10:24:28.813-07:00",
 
415
  "body": "This incident has been resolved.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "minor",
418
+ "last_seen": "2026-09-04T14:19:03Z",
419
  "resolved_at": "2026-04-20T12:06:08.090-07:00",
420
  "resolved_inferred": false,
421
  "started_at": "2026-04-20T09:00:01.381-07:00",
 
428
  "body": "This incident has been resolved.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "major",
431
+ "last_seen": "2026-09-04T14:19:03Z",
432
  "resolved_at": "2026-04-15T15:22:21.375-07:00",
433
  "resolved_inferred": false,
434
  "started_at": "2026-04-15T06:05:44.000-07:00",
 
441
  "body": "This incident has been resolved.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "major",
444
+ "last_seen": "2026-09-04T14:19:03Z",
445
  "resolved_at": "2026-04-13T13:45:57.496-07:00",
446
  "resolved_inferred": false,
447
  "started_at": "2026-04-13T12:27:46.882-07:00",
 
454
  "body": "This incident has been resolved.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "major",
457
+ "last_seen": "2026-09-04T14:19:03Z",
458
  "resolved_at": "2026-04-07T14:30:01.440-07:00",
459
  "resolved_inferred": false,
460
  "started_at": "2026-04-07T11:33:40.779-07:00",
 
467
  "body": "This incident has been resolved.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "major",
470
+ "last_seen": "2026-09-04T14:19:03Z",
471
  "resolved_at": "2026-04-06T13:04:36.164-07:00",
472
  "resolved_inferred": false,
473
  "started_at": "2026-04-06T11:36:19.790-07:00",
 
480
  "body": "This incident has been resolved.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "minor",
483
+ "last_seen": "2026-09-04T14:19:03Z",
484
  "resolved_at": "2026-04-06T11:35:46.595-07:00",
485
  "resolved_inferred": false,
486
  "started_at": "2026-03-31T11:51:23.000-07:00",
 
493
  "body": "This incident has been resolved.",
494
  "first_seen": "2026-09-04T07:06:16Z",
495
  "impact": "major",
496
+ "last_seen": "2026-09-04T14:19:03Z",
497
  "resolved_at": "2026-04-01T07:42:59.127-07:00",
498
  "resolved_inferred": false,
499
  "started_at": "2026-03-31T08:17:40.053-07:00",
 
506
  "body": "This incident has been resolved.",
507
  "first_seen": "2026-09-04T07:06:16Z",
508
  "impact": "none",
509
+ "last_seen": "2026-09-04T14:19:03Z",
510
  "resolved_at": "2026-03-27T09:29:47.155-07:00",
511
  "resolved_inferred": false,
512
  "started_at": "2026-03-26T12:32:24.804-07:00",
 
519
  "body": "This incident has been resolved.",
520
  "first_seen": "2026-09-04T07:06:16Z",
521
  "impact": "none",
522
+ "last_seen": "2026-09-04T14:19:03Z",
523
  "resolved_at": "2026-03-27T09:29:37.890-07:00",
524
  "resolved_inferred": false,
525
  "started_at": "2026-03-25T14:53:07.102-07:00",
 
532
  "body": "The situation has been fully resolved. All sites have been reviewed, and workflows are now progressing as expected. Thank you for your patience.",
533
  "first_seen": "2026-09-04T07:06:16Z",
534
  "impact": "minor",
535
+ "last_seen": "2026-09-04T14:19:03Z",
536
  "resolved_at": "2026-03-27T08:03:37.793-07:00",
537
  "resolved_inferred": false,
538
  "started_at": "2026-03-25T08:38:40.636-07:00",
 
545
  "body": "This incident has been resolved.",
546
  "first_seen": "2026-09-04T07:06:16Z",
547
  "impact": "minor",
548
+ "last_seen": "2026-09-04T14:19:03Z",
549
  "resolved_at": "2026-03-24T07:53:53.619-07:00",
550
  "resolved_inferred": false,
551
  "started_at": "2026-03-24T05:57:05.584-07:00",
 
558
  "body": "This incident has been resolved.",
559
  "first_seen": "2026-09-04T07:06:16Z",
560
  "impact": "minor",
561
+ "last_seen": "2026-09-04T14:19:03Z",
562
  "resolved_at": "2026-03-24T05:28:50.578-07:00",
563
  "resolved_inferred": false,
564
  "started_at": "2026-03-23T05:18:37.562-07:00",
 
571
  "body": "This incident has been resolved.",
572
  "first_seen": "2026-09-04T07:06:16Z",
573
  "impact": "none",
574
+ "last_seen": "2026-09-04T14:19:03Z",
575
  "resolved_at": "2026-03-18T05:10:11.644-07:00",
576
  "resolved_inferred": false,
577
  "started_at": "2026-03-17T10:31:34.680-07:00",
 
584
  "body": "This incident has been resolved.",
585
  "first_seen": "2026-09-04T07:06:16Z",
586
  "impact": "critical",
587
+ "last_seen": "2026-09-04T14:19:03Z",
588
  "resolved_at": "2026-03-16T14:43:45.439-07:00",
589
  "resolved_inferred": false,
590
  "started_at": "2026-03-16T09:51:03.119-07:00",
 
597
  "body": "This incident has been resolved.",
598
  "first_seen": "2026-09-04T07:06:16Z",
599
  "impact": "none",
600
+ "last_seen": "2026-09-04T14:19:03Z",
601
  "resolved_at": "2026-03-13T18:27:11.546-07:00",
602
  "resolved_inferred": false,
603
  "started_at": "2026-03-13T13:49:44.599-07:00",
 
610
  "body": "This incident has been resolved.",
611
  "first_seen": "2026-09-04T07:06:16Z",
612
  "impact": "minor",
613
+ "last_seen": "2026-09-04T14:19:03Z",
614
  "resolved_at": "2026-03-13T04:50:34.426-07:00",
615
  "resolved_inferred": false,
616
  "started_at": "2026-03-12T12:04:08.179-07:00",
 
623
  "body": "This incident has been resolved.",
624
  "first_seen": "2026-09-04T07:06:16Z",
625
  "impact": "minor",
626
+ "last_seen": "2026-09-04T14:19:03Z",
627
  "resolved_at": "2026-03-04T15:31:55.711-08:00",
628
  "resolved_inferred": false,
629
  "started_at": "2026-03-04T06:24:55.102-08:00",
 
636
  "body": "This incident has been resolved.",
637
  "first_seen": "2026-09-04T07:06:16Z",
638
  "impact": "none",
639
+ "last_seen": "2026-09-04T14:19:03Z",
640
  "resolved_at": "2026-03-03T12:01:47.776-08:00",
641
  "resolved_inferred": false,
642
  "started_at": "2026-03-02T09:55:11.500-08:00",
 
649
  "body": "This incident has been resolved.",
650
  "first_seen": "2026-09-04T07:06:16Z",
651
  "impact": "none",
652
+ "last_seen": "2026-09-04T14:19:03Z",
653
  "resolved_at": "2026-03-09T06:00:53.993-07:00",
654
  "resolved_inferred": false,
655
  "started_at": "2026-02-26T08:34:30.998-08:00",
api/v/opennode.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "opennode",
4
  "platform": "statuspage",
5
  "status_url": "https://status.opennode.co",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-04-02T21:56:11.037Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-04-02T21:28:21.512Z",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2025-09-23T16:12:29.893Z",
30
  "resolved_inferred": false,
31
  "started_at": "2025-09-23T13:03:03.048Z",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "none",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2025-09-06T17:36:32.424Z",
43
  "resolved_inferred": false,
44
  "started_at": "2025-09-06T17:00:41.852Z",
 
3
  "slug": "opennode",
4
  "platform": "statuspage",
5
  "status_url": "https://status.opennode.co",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-04-02T21:56:11.037Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-04-02T21:28:21.512Z",
 
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2025-09-23T16:12:29.893Z",
30
  "resolved_inferred": false,
31
  "started_at": "2025-09-23T13:03:03.048Z",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "none",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2025-09-06T17:36:32.424Z",
43
  "resolved_inferred": false,
44
  "started_at": "2025-09-06T17:00:41.852Z",
api/v/opensea.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "opensea",
4
  "platform": "statuspage",
5
  "status_url": "https://status.opensea.io",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "critical",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-07-01T23:41:20.127Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-07-01T18:06:55.000Z",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "critical",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2025-10-21T01:09:57.984Z",
30
  "resolved_inferred": false,
31
  "started_at": "2025-10-21T01:09:57.882Z",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2025-10-21T07:03:40.078Z",
43
  "resolved_inferred": false,
44
  "started_at": "2025-10-20T16:20:56.909Z",
 
3
  "slug": "opensea",
4
  "platform": "statuspage",
5
  "status_url": "https://status.opensea.io",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "critical",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-07-01T23:41:20.127Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-07-01T18:06:55.000Z",
 
25
  "body": "This incident has been resolved",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "critical",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2025-10-21T01:09:57.984Z",
30
  "resolved_inferred": false,
31
  "started_at": "2025-10-21T01:09:57.882Z",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2025-10-21T07:03:40.078Z",
43
  "resolved_inferred": false,
44
  "started_at": "2025-10-20T16:20:56.909Z",
api/v/opensrs.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "opensrs",
4
  "platform": "statuspage",
5
  "status_url": "https://www.opensrsstatus.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved. Phone support restored.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-09-01T20:14:02.105Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-01T17:44:04.844Z",
@@ -25,7 +25,7 @@
25
  "body": "Our Engineers have resolved the issue with domain resolution on systemdns.com at this time. \n \nThere should be no further issues with domain DNS resolution at this time.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-08-11T21:31:36.080Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-11T15:52:07.476Z",
@@ -38,7 +38,7 @@
38
  "body": "The services in Cluster B are stable and this incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-08-06T15:34:53.035Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-08-06T11:34:56.679Z",
@@ -51,7 +51,7 @@
51
  "body": "The Login issues with Cluster B have now been corrected. \n\nStart Time - 0948 UTC\nEnd Time - 1054 UTC",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-08-06T10:55:43.395Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-08-06T09:48:23.109Z",
@@ -64,7 +64,7 @@
64
  "body": "The connection issues with Identity Digital registry have been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-08-06T19:40:07.350Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-08-05T19:04:16.853Z",
@@ -77,7 +77,7 @@
77
  "body": "This incident has been resolved. All services are operating normally.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-08-05T19:41:50.883Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-08-05T16:18:13.976Z",
@@ -90,7 +90,7 @@
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-07-23T22:22:37.408Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-07-23T15:52:38.515Z",
@@ -103,7 +103,7 @@
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-07-02T02:53:58.095Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-07-02T01:21:47.731Z",
@@ -116,7 +116,7 @@
116
  "body": "All services have now been restored.\n\nStarted: 2026-06-17 18:58 UTC\nResolved: 2026-06-17 19:38 UTC",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-06-17T19:54:24.397Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-06-17T19:13:05.906Z",
@@ -129,7 +129,7 @@
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-06-14T15:09:29.998Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-06-14T14:28:45.410Z",
@@ -142,7 +142,7 @@
142
  "body": "There was an issue with the antivirus servers, which caused the service to fail and emails to be rejected.\n\nA fix has been implemented, and the Anti-virus services are operational.\n\nThis incident has been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "minor",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2026-05-12T16:39:35.677Z",
147
  "resolved_inferred": false,
148
  "started_at": "2026-05-12T16:18:54.422Z",
@@ -155,7 +155,7 @@
155
  "body": "The login issue with the Reseller Control Panel is now resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "minor",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2026-04-23T18:40:38.296Z",
160
  "resolved_inferred": false,
161
  "started_at": "2026-04-23T18:08:55.616Z",
@@ -168,7 +168,7 @@
168
  "body": "Engineering has applied a fix and the issue has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "minor",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2026-04-22T20:45:35.056Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-04-22T20:41:36.860Z",
@@ -181,7 +181,7 @@
181
  "body": "We have identified and corrected the issue and domain lookups for .ai, .llc and .center are now restored.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "minor",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2026-04-19T12:22:02.589Z",
186
  "resolved_inferred": false,
187
  "started_at": "2026-04-19T10:55:40.905Z",
@@ -194,7 +194,7 @@
194
  "body": "Thank you for your patience, this issue has now been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2026-04-16T11:12:24.478Z",
199
  "resolved_inferred": false,
200
  "started_at": "2026-04-16T09:43:47.738Z",
@@ -207,7 +207,7 @@
207
  "body": "This incident has been resolved",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "minor",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2026-04-05T01:24:16.519Z",
212
  "resolved_inferred": false,
213
  "started_at": "2026-04-04T16:49:33.287Z",
@@ -220,7 +220,7 @@
220
  "body": "That you for your patience. The Cluster B issues have now been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2026-04-04T12:14:49.798Z",
225
  "resolved_inferred": false,
226
  "started_at": "2026-04-04T10:58:16.060Z",
@@ -233,7 +233,7 @@
233
  "body": "Our connections are now stable for ccTLDs. \n\nThis incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "minor",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2026-04-02T15:15:25.344Z",
238
  "resolved_inferred": false,
239
  "started_at": "2026-04-02T13:28:46.094Z",
@@ -246,7 +246,7 @@
246
  "body": "We've monitored our connections for latency and see it's been stable, not affecting .de and .fr domains requests and actions on them.\n\nThis incidence has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "minor",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2026-04-01T18:26:02.266Z",
251
  "resolved_inferred": false,
252
  "started_at": "2026-04-01T14:30:46.481Z",
@@ -259,7 +259,7 @@
259
  "body": "Engineering has applied a fix. This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "minor",
262
- "last_seen": "2026-09-04T12:24:18Z",
263
  "resolved_at": "2026-03-20T20:02:32.964Z",
264
  "resolved_inferred": false,
265
  "started_at": "2026-03-20T19:21:24.699Z",
@@ -272,7 +272,7 @@
272
  "body": "The connection issues have been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "minor",
275
- "last_seen": "2026-09-04T12:24:18Z",
276
  "resolved_at": "2026-03-12T15:18:38.689Z",
277
  "resolved_inferred": false,
278
  "started_at": "2026-03-12T13:23:42.917Z",
@@ -285,7 +285,7 @@
285
  "body": "Engineering has implemented a fix which has resovled this incident.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "minor",
288
- "last_seen": "2026-09-04T12:24:18Z",
289
  "resolved_at": "2026-03-10T15:46:25.465Z",
290
  "resolved_inferred": false,
291
  "started_at": "2026-03-10T15:13:09.867Z",
@@ -298,7 +298,7 @@
298
  "body": "The registry team has resolved the issues in their system and the connections are operational on our end.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "minor",
301
- "last_seen": "2026-09-04T12:24:18Z",
302
  "resolved_at": "2026-03-05T17:13:16.907Z",
303
  "resolved_inferred": false,
304
  "started_at": "2026-03-05T16:19:40.135Z",
@@ -311,7 +311,7 @@
311
  "body": "Engineering has issued a fix and services have returned to normal. This incident is resolved.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "minor",
314
- "last_seen": "2026-09-04T12:24:18Z",
315
  "resolved_at": "2026-03-03T14:58:45.656Z",
316
  "resolved_inferred": false,
317
  "started_at": "2026-03-03T09:43:00.936Z",
@@ -324,7 +324,7 @@
324
  "body": "Our Engineers have identified the issues with Epag managed ccTLDs, and resolved the issues at this time.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "minor",
327
- "last_seen": "2026-09-04T12:24:18Z",
328
  "resolved_at": "2026-02-27T21:58:39.308Z",
329
  "resolved_inferred": false,
330
  "started_at": "2026-02-27T21:13:05.013Z",
@@ -337,7 +337,7 @@
337
  "body": "Engineering has issued a fix and services have returned to normal. This incident is resolved.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "minor",
340
- "last_seen": "2026-09-04T12:24:18Z",
341
  "resolved_at": "2026-02-26T18:49:05.021Z",
342
  "resolved_inferred": false,
343
  "started_at": "2026-02-26T18:19:48.822Z",
@@ -350,7 +350,7 @@
350
  "body": "This incident has been resolved.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "minor",
353
- "last_seen": "2026-09-04T12:24:18Z",
354
  "resolved_at": "2026-02-25T16:43:37.038Z",
355
  "resolved_inferred": false,
356
  "started_at": "2026-02-25T15:57:24.404Z",
@@ -363,7 +363,7 @@
363
  "body": "Our Engineers have resolved the issue with DNS records being removed when attempting to update the existing records.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "minor",
366
- "last_seen": "2026-09-04T12:24:18Z",
367
  "resolved_at": "2026-02-25T03:53:08.234Z",
368
  "resolved_inferred": false,
369
  "started_at": "2026-02-24T21:59:02.747Z",
@@ -376,7 +376,7 @@
376
  "body": "Services have recovered and the incident has been resolved.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "minor",
379
- "last_seen": "2026-09-04T12:24:18Z",
380
  "resolved_at": "2026-02-03T22:10:49.738Z",
381
  "resolved_inferred": false,
382
  "started_at": "2026-02-03T16:05:31.823Z",
@@ -389,7 +389,7 @@
389
  "body": "The latency issue being experienced with the API has been resolved. \n\nOur Engineers will maintain their monitoring.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "minor",
392
- "last_seen": "2026-09-04T12:24:18Z",
393
  "resolved_at": "2026-01-29T22:43:04.408Z",
394
  "resolved_inferred": false,
395
  "started_at": "2026-01-29T16:39:45.037Z",
@@ -402,7 +402,7 @@
402
  "body": "This incident has been resolved. Phone support is fully restored.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "minor",
405
- "last_seen": "2026-09-04T12:24:18Z",
406
  "resolved_at": "2026-01-13T20:46:25.000Z",
407
  "resolved_inferred": false,
408
  "started_at": "2026-01-13T17:42:29.233Z",
@@ -415,7 +415,7 @@
415
  "body": "This issue has now been resolved.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "minor",
418
- "last_seen": "2026-09-04T12:24:18Z",
419
  "resolved_at": "2026-01-13T17:42:41.923Z",
420
  "resolved_inferred": false,
421
  "started_at": "2026-01-13T17:16:51.462Z",
@@ -428,7 +428,7 @@
428
  "body": "Our engineering team identified a DDoS attack impacting resolution of the NS1\u2013NS3 nameservers, causing the timeout of multiple sites. This incident was resolved.\n\nStart Time: 3:00 UTC\nEnd Time: 4:30 UTC\nTotal: 1h, 30m",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "none",
431
- "last_seen": "2026-09-04T12:24:18Z",
432
  "resolved_at": "2026-01-01T08:00:00.000Z",
433
  "resolved_inferred": false,
434
  "started_at": "2026-01-01T08:00:00.000Z",
@@ -441,7 +441,7 @@
441
  "body": "This incident has been resolved.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "minor",
444
- "last_seen": "2026-09-04T12:24:18Z",
445
  "resolved_at": "2025-12-06T17:57:10.008Z",
446
  "resolved_inferred": false,
447
  "started_at": "2025-12-06T16:47:39.906Z",
@@ -454,7 +454,7 @@
454
  "body": "The 3rd party issues have now been resolved, and our Ticketing and Chat systems are back up and running. We appreciate your patience.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "minor",
457
- "last_seen": "2026-09-04T12:24:18Z",
458
  "resolved_at": "2025-12-05T10:23:51.147Z",
459
  "resolved_inferred": false,
460
  "started_at": "2025-12-05T09:36:32.425Z",
@@ -467,7 +467,7 @@
467
  "body": "This incident has been resolved.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "minor",
470
- "last_seen": "2026-09-04T12:24:18Z",
471
  "resolved_at": "2025-12-02T19:27:25.316Z",
472
  "resolved_inferred": false,
473
  "started_at": "2025-12-02T17:49:26.508Z",
@@ -480,7 +480,7 @@
480
  "body": "This incident has been resolved.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "minor",
483
- "last_seen": "2026-09-04T12:24:18Z",
484
  "resolved_at": "2025-12-01T03:08:44.439Z",
485
  "resolved_inferred": false,
486
  "started_at": "2025-12-01T02:26:29.836Z",
@@ -493,7 +493,7 @@
493
  "body": "The issue affecting OpenSRS.COM has been resolved at this time. \n\nStart: Wed 19 Nov 2025 10:40 UTC\nEnd: Thu 20 Nov 2025 01:10:00 UTC",
494
  "first_seen": "2026-09-04T07:06:16Z",
495
  "impact": "minor",
496
- "last_seen": "2026-09-04T12:24:18Z",
497
  "resolved_at": "2025-11-20T01:12:39.250Z",
498
  "resolved_inferred": false,
499
  "started_at": "2025-11-19T23:15:28.663Z",
@@ -506,7 +506,7 @@
506
  "body": "This issue is now resolved.\n\nStart: Tuesday, November 17, 2025 16:24 UTC\nEnd: Tuesday, November 17, 2025 16:47 UTC",
507
  "first_seen": "2026-09-04T07:06:16Z",
508
  "impact": "minor",
509
- "last_seen": "2026-09-04T12:24:18Z",
510
  "resolved_at": "2025-11-17T16:49:49.805Z",
511
  "resolved_inferred": false,
512
  "started_at": "2025-11-17T16:37:33.893Z",
@@ -519,7 +519,7 @@
519
  "body": "The connection to the .CO registry is stable. This incident has been resolved.",
520
  "first_seen": "2026-09-04T07:06:16Z",
521
  "impact": "minor",
522
- "last_seen": "2026-09-04T12:24:18Z",
523
  "resolved_at": "2025-10-31T20:56:00.278Z",
524
  "resolved_inferred": false,
525
  "started_at": "2025-10-31T19:22:24.366Z",
@@ -532,7 +532,7 @@
532
  "body": "We were able to identify and resolve the issue impacting our Reseller Control Panel.",
533
  "first_seen": "2026-09-04T07:06:16Z",
534
  "impact": "minor",
535
- "last_seen": "2026-09-04T12:24:18Z",
536
  "resolved_at": "2025-10-15T15:00:56.264Z",
537
  "resolved_inferred": false,
538
  "started_at": "2025-10-15T14:48:10.501Z",
@@ -545,7 +545,7 @@
545
  "body": "Thank you for your patience. Our engineers have now resolved the domain lookup failures with OpenSRS. All systems are good.\n\nStart time 21:48 UTC\nEnd Time 06:46 UTC",
546
  "first_seen": "2026-09-04T07:06:16Z",
547
  "impact": "minor",
548
- "last_seen": "2026-09-04T12:24:18Z",
549
  "resolved_at": "2025-10-11T07:03:36.910Z",
550
  "resolved_inferred": false,
551
  "started_at": "2025-10-10T21:48:29.382Z",
@@ -558,7 +558,7 @@
558
  "body": "Our issue regarding order processing support for Digicert SSL orders has been resolved.",
559
  "first_seen": "2026-09-04T07:06:16Z",
560
  "impact": "none",
561
- "last_seen": "2026-09-04T12:24:18Z",
562
  "resolved_at": "2025-09-23T20:35:51.747Z",
563
  "resolved_inferred": false,
564
  "started_at": "2025-09-23T19:19:49.606Z",
@@ -571,7 +571,7 @@
571
  "body": "This incident has been resolved.",
572
  "first_seen": "2026-09-04T07:06:16Z",
573
  "impact": "minor",
574
- "last_seen": "2026-09-04T12:24:18Z",
575
  "resolved_at": "2025-09-15T15:53:39.900Z",
576
  "resolved_inferred": false,
577
  "started_at": "2025-09-15T14:02:32.029Z",
@@ -584,7 +584,7 @@
584
  "body": "This incident has been resolved.",
585
  "first_seen": "2026-09-04T07:06:16Z",
586
  "impact": "minor",
587
- "last_seen": "2026-09-04T12:24:18Z",
588
  "resolved_at": "2025-09-05T16:36:48.579Z",
589
  "resolved_inferred": false,
590
  "started_at": "2025-09-05T12:31:11.933Z",
@@ -597,7 +597,7 @@
597
  "body": "There was a certificate renewal at the registry which caused connection failures. CIRA reverted the certificate to restore these connections. This incident has been resolved.",
598
  "first_seen": "2026-09-04T07:06:16Z",
599
  "impact": "minor",
600
- "last_seen": "2026-09-04T12:24:18Z",
601
  "resolved_at": "2025-08-22T18:43:55.760Z",
602
  "resolved_inferred": false,
603
  "started_at": "2025-08-22T10:48:47.241Z",
@@ -610,7 +610,7 @@
610
  "body": "Our engineers have applied a fix, and confirmed webmail for Cluster B is now back to operating as usual.\n\nStarted: Tuesday August 19th at 20:40 UTC\nEnded: Tuesday August 19th at 21:09 UTC",
611
  "first_seen": "2026-09-04T07:06:16Z",
612
  "impact": "minor",
613
- "last_seen": "2026-09-04T12:24:18Z",
614
  "resolved_at": "2025-08-19T20:16:44.524Z",
615
  "resolved_inferred": false,
616
  "started_at": "2025-08-19T19:47:42.620Z",
@@ -623,7 +623,7 @@
623
  "body": "Thank you for your patience, our NoC has identified and resolved the login issues at this time. \n\nStart time: 23:25 UTC\nEnd Time: 00:58 UTC\nDuration: 1H 33M",
624
  "first_seen": "2026-09-04T07:06:16Z",
625
  "impact": "minor",
626
- "last_seen": "2026-09-04T12:24:18Z",
627
  "resolved_at": "2025-08-06T01:10:47.965Z",
628
  "resolved_inferred": false,
629
  "started_at": "2025-08-05T23:53:34.780Z",
 
3
  "slug": "opensrs",
4
  "platform": "statuspage",
5
  "status_url": "https://www.opensrsstatus.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved. Phone support restored.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-09-01T20:14:02.105Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-01T17:44:04.844Z",
 
25
  "body": "Our Engineers have resolved the issue with domain resolution on systemdns.com at this time. \n \nThere should be no further issues with domain DNS resolution at this time.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-08-11T21:31:36.080Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-11T15:52:07.476Z",
 
38
  "body": "The services in Cluster B are stable and this incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-08-06T15:34:53.035Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-08-06T11:34:56.679Z",
 
51
  "body": "The Login issues with Cluster B have now been corrected. \n\nStart Time - 0948 UTC\nEnd Time - 1054 UTC",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-08-06T10:55:43.395Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-08-06T09:48:23.109Z",
 
64
  "body": "The connection issues with Identity Digital registry have been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-08-06T19:40:07.350Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-08-05T19:04:16.853Z",
 
77
  "body": "This incident has been resolved. All services are operating normally.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-08-05T19:41:50.883Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-08-05T16:18:13.976Z",
 
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-07-23T22:22:37.408Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-07-23T15:52:38.515Z",
 
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-07-02T02:53:58.095Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-07-02T01:21:47.731Z",
 
116
  "body": "All services have now been restored.\n\nStarted: 2026-06-17 18:58 UTC\nResolved: 2026-06-17 19:38 UTC",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-06-17T19:54:24.397Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-06-17T19:13:05.906Z",
 
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-06-14T15:09:29.998Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-06-14T14:28:45.410Z",
 
142
  "body": "There was an issue with the antivirus servers, which caused the service to fail and emails to be rejected.\n\nA fix has been implemented, and the Anti-virus services are operational.\n\nThis incident has been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "minor",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2026-05-12T16:39:35.677Z",
147
  "resolved_inferred": false,
148
  "started_at": "2026-05-12T16:18:54.422Z",
 
155
  "body": "The login issue with the Reseller Control Panel is now resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "minor",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2026-04-23T18:40:38.296Z",
160
  "resolved_inferred": false,
161
  "started_at": "2026-04-23T18:08:55.616Z",
 
168
  "body": "Engineering has applied a fix and the issue has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "minor",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2026-04-22T20:45:35.056Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-04-22T20:41:36.860Z",
 
181
  "body": "We have identified and corrected the issue and domain lookups for .ai, .llc and .center are now restored.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "minor",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2026-04-19T12:22:02.589Z",
186
  "resolved_inferred": false,
187
  "started_at": "2026-04-19T10:55:40.905Z",
 
194
  "body": "Thank you for your patience, this issue has now been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2026-04-16T11:12:24.478Z",
199
  "resolved_inferred": false,
200
  "started_at": "2026-04-16T09:43:47.738Z",
 
207
  "body": "This incident has been resolved",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "minor",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2026-04-05T01:24:16.519Z",
212
  "resolved_inferred": false,
213
  "started_at": "2026-04-04T16:49:33.287Z",
 
220
  "body": "That you for your patience. The Cluster B issues have now been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2026-04-04T12:14:49.798Z",
225
  "resolved_inferred": false,
226
  "started_at": "2026-04-04T10:58:16.060Z",
 
233
  "body": "Our connections are now stable for ccTLDs. \n\nThis incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "minor",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2026-04-02T15:15:25.344Z",
238
  "resolved_inferred": false,
239
  "started_at": "2026-04-02T13:28:46.094Z",
 
246
  "body": "We've monitored our connections for latency and see it's been stable, not affecting .de and .fr domains requests and actions on them.\n\nThis incidence has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "minor",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2026-04-01T18:26:02.266Z",
251
  "resolved_inferred": false,
252
  "started_at": "2026-04-01T14:30:46.481Z",
 
259
  "body": "Engineering has applied a fix. This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "minor",
262
+ "last_seen": "2026-09-04T14:19:03Z",
263
  "resolved_at": "2026-03-20T20:02:32.964Z",
264
  "resolved_inferred": false,
265
  "started_at": "2026-03-20T19:21:24.699Z",
 
272
  "body": "The connection issues have been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "minor",
275
+ "last_seen": "2026-09-04T14:19:03Z",
276
  "resolved_at": "2026-03-12T15:18:38.689Z",
277
  "resolved_inferred": false,
278
  "started_at": "2026-03-12T13:23:42.917Z",
 
285
  "body": "Engineering has implemented a fix which has resovled this incident.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "minor",
288
+ "last_seen": "2026-09-04T14:19:03Z",
289
  "resolved_at": "2026-03-10T15:46:25.465Z",
290
  "resolved_inferred": false,
291
  "started_at": "2026-03-10T15:13:09.867Z",
 
298
  "body": "The registry team has resolved the issues in their system and the connections are operational on our end.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "minor",
301
+ "last_seen": "2026-09-04T14:19:03Z",
302
  "resolved_at": "2026-03-05T17:13:16.907Z",
303
  "resolved_inferred": false,
304
  "started_at": "2026-03-05T16:19:40.135Z",
 
311
  "body": "Engineering has issued a fix and services have returned to normal. This incident is resolved.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "minor",
314
+ "last_seen": "2026-09-04T14:19:03Z",
315
  "resolved_at": "2026-03-03T14:58:45.656Z",
316
  "resolved_inferred": false,
317
  "started_at": "2026-03-03T09:43:00.936Z",
 
324
  "body": "Our Engineers have identified the issues with Epag managed ccTLDs, and resolved the issues at this time.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "minor",
327
+ "last_seen": "2026-09-04T14:19:03Z",
328
  "resolved_at": "2026-02-27T21:58:39.308Z",
329
  "resolved_inferred": false,
330
  "started_at": "2026-02-27T21:13:05.013Z",
 
337
  "body": "Engineering has issued a fix and services have returned to normal. This incident is resolved.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "minor",
340
+ "last_seen": "2026-09-04T14:19:03Z",
341
  "resolved_at": "2026-02-26T18:49:05.021Z",
342
  "resolved_inferred": false,
343
  "started_at": "2026-02-26T18:19:48.822Z",
 
350
  "body": "This incident has been resolved.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "minor",
353
+ "last_seen": "2026-09-04T14:19:03Z",
354
  "resolved_at": "2026-02-25T16:43:37.038Z",
355
  "resolved_inferred": false,
356
  "started_at": "2026-02-25T15:57:24.404Z",
 
363
  "body": "Our Engineers have resolved the issue with DNS records being removed when attempting to update the existing records.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "minor",
366
+ "last_seen": "2026-09-04T14:19:03Z",
367
  "resolved_at": "2026-02-25T03:53:08.234Z",
368
  "resolved_inferred": false,
369
  "started_at": "2026-02-24T21:59:02.747Z",
 
376
  "body": "Services have recovered and the incident has been resolved.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "minor",
379
+ "last_seen": "2026-09-04T14:19:03Z",
380
  "resolved_at": "2026-02-03T22:10:49.738Z",
381
  "resolved_inferred": false,
382
  "started_at": "2026-02-03T16:05:31.823Z",
 
389
  "body": "The latency issue being experienced with the API has been resolved. \n\nOur Engineers will maintain their monitoring.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "minor",
392
+ "last_seen": "2026-09-04T14:19:03Z",
393
  "resolved_at": "2026-01-29T22:43:04.408Z",
394
  "resolved_inferred": false,
395
  "started_at": "2026-01-29T16:39:45.037Z",
 
402
  "body": "This incident has been resolved. Phone support is fully restored.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "minor",
405
+ "last_seen": "2026-09-04T14:19:03Z",
406
  "resolved_at": "2026-01-13T20:46:25.000Z",
407
  "resolved_inferred": false,
408
  "started_at": "2026-01-13T17:42:29.233Z",
 
415
  "body": "This issue has now been resolved.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "minor",
418
+ "last_seen": "2026-09-04T14:19:03Z",
419
  "resolved_at": "2026-01-13T17:42:41.923Z",
420
  "resolved_inferred": false,
421
  "started_at": "2026-01-13T17:16:51.462Z",
 
428
  "body": "Our engineering team identified a DDoS attack impacting resolution of the NS1\u2013NS3 nameservers, causing the timeout of multiple sites. This incident was resolved.\n\nStart Time: 3:00 UTC\nEnd Time: 4:30 UTC\nTotal: 1h, 30m",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "none",
431
+ "last_seen": "2026-09-04T14:19:03Z",
432
  "resolved_at": "2026-01-01T08:00:00.000Z",
433
  "resolved_inferred": false,
434
  "started_at": "2026-01-01T08:00:00.000Z",
 
441
  "body": "This incident has been resolved.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "minor",
444
+ "last_seen": "2026-09-04T14:19:03Z",
445
  "resolved_at": "2025-12-06T17:57:10.008Z",
446
  "resolved_inferred": false,
447
  "started_at": "2025-12-06T16:47:39.906Z",
 
454
  "body": "The 3rd party issues have now been resolved, and our Ticketing and Chat systems are back up and running. We appreciate your patience.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "minor",
457
+ "last_seen": "2026-09-04T14:19:03Z",
458
  "resolved_at": "2025-12-05T10:23:51.147Z",
459
  "resolved_inferred": false,
460
  "started_at": "2025-12-05T09:36:32.425Z",
 
467
  "body": "This incident has been resolved.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "minor",
470
+ "last_seen": "2026-09-04T14:19:03Z",
471
  "resolved_at": "2025-12-02T19:27:25.316Z",
472
  "resolved_inferred": false,
473
  "started_at": "2025-12-02T17:49:26.508Z",
 
480
  "body": "This incident has been resolved.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "minor",
483
+ "last_seen": "2026-09-04T14:19:03Z",
484
  "resolved_at": "2025-12-01T03:08:44.439Z",
485
  "resolved_inferred": false,
486
  "started_at": "2025-12-01T02:26:29.836Z",
 
493
  "body": "The issue affecting OpenSRS.COM has been resolved at this time. \n\nStart: Wed 19 Nov 2025 10:40 UTC\nEnd: Thu 20 Nov 2025 01:10:00 UTC",
494
  "first_seen": "2026-09-04T07:06:16Z",
495
  "impact": "minor",
496
+ "last_seen": "2026-09-04T14:19:03Z",
497
  "resolved_at": "2025-11-20T01:12:39.250Z",
498
  "resolved_inferred": false,
499
  "started_at": "2025-11-19T23:15:28.663Z",
 
506
  "body": "This issue is now resolved.\n\nStart: Tuesday, November 17, 2025 16:24 UTC\nEnd: Tuesday, November 17, 2025 16:47 UTC",
507
  "first_seen": "2026-09-04T07:06:16Z",
508
  "impact": "minor",
509
+ "last_seen": "2026-09-04T14:19:03Z",
510
  "resolved_at": "2025-11-17T16:49:49.805Z",
511
  "resolved_inferred": false,
512
  "started_at": "2025-11-17T16:37:33.893Z",
 
519
  "body": "The connection to the .CO registry is stable. This incident has been resolved.",
520
  "first_seen": "2026-09-04T07:06:16Z",
521
  "impact": "minor",
522
+ "last_seen": "2026-09-04T14:19:03Z",
523
  "resolved_at": "2025-10-31T20:56:00.278Z",
524
  "resolved_inferred": false,
525
  "started_at": "2025-10-31T19:22:24.366Z",
 
532
  "body": "We were able to identify and resolve the issue impacting our Reseller Control Panel.",
533
  "first_seen": "2026-09-04T07:06:16Z",
534
  "impact": "minor",
535
+ "last_seen": "2026-09-04T14:19:03Z",
536
  "resolved_at": "2025-10-15T15:00:56.264Z",
537
  "resolved_inferred": false,
538
  "started_at": "2025-10-15T14:48:10.501Z",
 
545
  "body": "Thank you for your patience. Our engineers have now resolved the domain lookup failures with OpenSRS. All systems are good.\n\nStart time 21:48 UTC\nEnd Time 06:46 UTC",
546
  "first_seen": "2026-09-04T07:06:16Z",
547
  "impact": "minor",
548
+ "last_seen": "2026-09-04T14:19:03Z",
549
  "resolved_at": "2025-10-11T07:03:36.910Z",
550
  "resolved_inferred": false,
551
  "started_at": "2025-10-10T21:48:29.382Z",
 
558
  "body": "Our issue regarding order processing support for Digicert SSL orders has been resolved.",
559
  "first_seen": "2026-09-04T07:06:16Z",
560
  "impact": "none",
561
+ "last_seen": "2026-09-04T14:19:03Z",
562
  "resolved_at": "2025-09-23T20:35:51.747Z",
563
  "resolved_inferred": false,
564
  "started_at": "2025-09-23T19:19:49.606Z",
 
571
  "body": "This incident has been resolved.",
572
  "first_seen": "2026-09-04T07:06:16Z",
573
  "impact": "minor",
574
+ "last_seen": "2026-09-04T14:19:03Z",
575
  "resolved_at": "2025-09-15T15:53:39.900Z",
576
  "resolved_inferred": false,
577
  "started_at": "2025-09-15T14:02:32.029Z",
 
584
  "body": "This incident has been resolved.",
585
  "first_seen": "2026-09-04T07:06:16Z",
586
  "impact": "minor",
587
+ "last_seen": "2026-09-04T14:19:03Z",
588
  "resolved_at": "2025-09-05T16:36:48.579Z",
589
  "resolved_inferred": false,
590
  "started_at": "2025-09-05T12:31:11.933Z",
 
597
  "body": "There was a certificate renewal at the registry which caused connection failures. CIRA reverted the certificate to restore these connections. This incident has been resolved.",
598
  "first_seen": "2026-09-04T07:06:16Z",
599
  "impact": "minor",
600
+ "last_seen": "2026-09-04T14:19:03Z",
601
  "resolved_at": "2025-08-22T18:43:55.760Z",
602
  "resolved_inferred": false,
603
  "started_at": "2025-08-22T10:48:47.241Z",
 
610
  "body": "Our engineers have applied a fix, and confirmed webmail for Cluster B is now back to operating as usual.\n\nStarted: Tuesday August 19th at 20:40 UTC\nEnded: Tuesday August 19th at 21:09 UTC",
611
  "first_seen": "2026-09-04T07:06:16Z",
612
  "impact": "minor",
613
+ "last_seen": "2026-09-04T14:19:03Z",
614
  "resolved_at": "2025-08-19T20:16:44.524Z",
615
  "resolved_inferred": false,
616
  "started_at": "2025-08-19T19:47:42.620Z",
 
623
  "body": "Thank you for your patience, our NoC has identified and resolved the login issues at this time. \n\nStart time: 23:25 UTC\nEnd Time: 00:58 UTC\nDuration: 1H 33M",
624
  "first_seen": "2026-09-04T07:06:16Z",
625
  "impact": "minor",
626
+ "last_seen": "2026-09-04T14:19:03Z",
627
  "resolved_at": "2025-08-06T01:10:47.965Z",
628
  "resolved_inferred": false,
629
  "started_at": "2025-08-05T23:53:34.780Z",
api/v/openvpn.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "openvpn",
4
  "platform": "statuspage",
5
  "status_url": "https://status.openvpn.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-07-21T17:49:14.674Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-07-21T15:17:00.287Z",
@@ -25,7 +25,7 @@
25
  "body": "The CloudConnexa Region Milan is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-07-21T15:02:54.310Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-07-20T11:59:08.443Z",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-07-09T21:32:00.915Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-07-08T21:31:52.473Z",
@@ -51,7 +51,7 @@
51
  "body": "The CloudConnexa Region Finland is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-06-05T15:38:34.669Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-06-04T15:42:12.680Z",
@@ -64,7 +64,7 @@
64
  "body": "The CloudConnexa Region, Finland, is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-05-20T01:48:25.763Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-05-19T18:43:07.596Z",
@@ -77,7 +77,7 @@
77
  "body": "The CloudConnexa Region, Johannesburg, is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-05-19T13:17:36.399Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-05-19T10:00:39.483Z",
@@ -90,7 +90,7 @@
90
  "body": "The issue affecting the CloudConnexa Status page and email notifications about connector statuses has been resolved. If you continue to experience any issues, please contact Support. Thank you for your patience.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-04-19T04:42:31.000Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-04-19T03:43:01.000Z",
@@ -103,7 +103,7 @@
103
  "body": "The CloudConnexa Region Sydney is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-04-16T08:30:53.458Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-04-15T17:32:53.981Z",
@@ -116,7 +116,7 @@
116
  "body": "The CloudConnexa Amsterdam Region for IPsec is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-04-02T13:20:31.934Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-04-01T09:09:36.027Z",
@@ -129,7 +129,7 @@
129
  "body": "This issue, related to the problems reported on slowness within the tunnel, has now been resolved. \n\nIf you continue to experience any issues, please reach out to Support. Thank you for your patience.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-03-22T13:54:06.390Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-03-21T13:16:11.000Z",
@@ -142,7 +142,7 @@
142
  "body": "This issue related to the Import Profile via URL functionality in OpenVPN Connect when connecting through CloudConnexa has now been resolved. \n\nIf you continue to experience any issues, please reach out to Support. Thank you for your patience.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "minor",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2025-12-19T12:25:09.007Z",
147
  "resolved_inferred": false,
148
  "started_at": "2025-12-19T10:28:13.446Z",
@@ -155,7 +155,7 @@
155
  "body": "S\u00e3o Paulo CloudConnexa Region issue is resolved. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "minor",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2025-12-16T15:26:10.451Z",
160
  "resolved_inferred": false,
161
  "started_at": "2025-12-12T20:17:56.467Z",
@@ -168,7 +168,7 @@
168
  "body": "CloudConnexa Importing Profile is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "minor",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2025-11-27T15:53:24.624Z",
173
  "resolved_inferred": false,
174
  "started_at": "2025-11-27T04:12:14.726Z",
@@ -181,7 +181,7 @@
181
  "body": "The portals are back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "minor",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2025-11-26T23:39:52.067Z",
186
  "resolved_inferred": false,
187
  "started_at": "2025-11-26T21:58:21.223Z",
@@ -194,7 +194,7 @@
194
  "body": "IPsec Connector (HA/Redundant Setup) case is resolved. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2026-01-27T12:08:02.472Z",
199
  "resolved_inferred": false,
200
  "started_at": "2025-11-25T15:13:51.083Z",
@@ -207,7 +207,7 @@
207
  "body": "The CloudConnexa Region, Singapore, is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "minor",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2025-11-21T16:53:14.233Z",
212
  "resolved_inferred": false,
213
  "started_at": "2025-11-21T12:04:07.641Z",
@@ -220,7 +220,7 @@
220
  "body": "The CloudConnexa portal is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2025-11-18T18:01:40.360Z",
225
  "resolved_inferred": false,
226
  "started_at": "2025-11-18T12:06:19.695Z",
@@ -233,7 +233,7 @@
233
  "body": "The CloudConnexa Region, Toronto, Canada, is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "none",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2025-10-27T20:02:18.544Z",
238
  "resolved_inferred": false,
239
  "started_at": "2025-10-24T14:06:20.000Z",
@@ -246,7 +246,7 @@
246
  "body": "Services is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "minor",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2025-10-03T08:03:34.474Z",
251
  "resolved_inferred": false,
252
  "started_at": "2025-10-03T01:17:46.616Z",
@@ -259,7 +259,7 @@
259
  "body": "Brussels and London CloudConnexa Region issues is resolved. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "minor",
262
- "last_seen": "2026-09-04T12:24:18Z",
263
  "resolved_at": "2025-10-09T15:36:45.998Z",
264
  "resolved_inferred": false,
265
  "started_at": "2025-10-02T11:11:26.000Z",
@@ -272,7 +272,7 @@
272
  "body": "CloudConnexa Portal is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "major",
275
- "last_seen": "2026-09-04T12:24:18Z",
276
  "resolved_at": "2025-09-24T14:21:55.268Z",
277
  "resolved_inferred": false,
278
  "started_at": "2025-09-24T09:49:54.120Z",
@@ -285,7 +285,7 @@
285
  "body": "The CloudConnexa London Region for IPsec is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "minor",
288
- "last_seen": "2026-09-04T12:24:18Z",
289
  "resolved_at": "2025-09-11T07:38:11.386Z",
290
  "resolved_inferred": false,
291
  "started_at": "2025-09-10T12:08:08.366Z",
@@ -298,7 +298,7 @@
298
  "body": "Columbus CloudConnexa region issue is resolved. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "minor",
301
- "last_seen": "2026-09-04T12:24:18Z",
302
  "resolved_at": "2025-08-20T12:19:18.793Z",
303
  "resolved_inferred": false,
304
  "started_at": "2025-08-20T10:57:20.478Z",
 
3
  "slug": "openvpn",
4
  "platform": "statuspage",
5
  "status_url": "https://status.openvpn.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-07-21T17:49:14.674Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-07-21T15:17:00.287Z",
 
25
  "body": "The CloudConnexa Region Milan is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-07-21T15:02:54.310Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-07-20T11:59:08.443Z",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-07-09T21:32:00.915Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-07-08T21:31:52.473Z",
 
51
  "body": "The CloudConnexa Region Finland is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-06-05T15:38:34.669Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-06-04T15:42:12.680Z",
 
64
  "body": "The CloudConnexa Region, Finland, is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-05-20T01:48:25.763Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-05-19T18:43:07.596Z",
 
77
  "body": "The CloudConnexa Region, Johannesburg, is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-05-19T13:17:36.399Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-05-19T10:00:39.483Z",
 
90
  "body": "The issue affecting the CloudConnexa Status page and email notifications about connector statuses has been resolved. If you continue to experience any issues, please contact Support. Thank you for your patience.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-04-19T04:42:31.000Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-04-19T03:43:01.000Z",
 
103
  "body": "The CloudConnexa Region Sydney is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-04-16T08:30:53.458Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-04-15T17:32:53.981Z",
 
116
  "body": "The CloudConnexa Amsterdam Region for IPsec is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-04-02T13:20:31.934Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-04-01T09:09:36.027Z",
 
129
  "body": "This issue, related to the problems reported on slowness within the tunnel, has now been resolved. \n\nIf you continue to experience any issues, please reach out to Support. Thank you for your patience.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-03-22T13:54:06.390Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-03-21T13:16:11.000Z",
 
142
  "body": "This issue related to the Import Profile via URL functionality in OpenVPN Connect when connecting through CloudConnexa has now been resolved. \n\nIf you continue to experience any issues, please reach out to Support. Thank you for your patience.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "minor",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2025-12-19T12:25:09.007Z",
147
  "resolved_inferred": false,
148
  "started_at": "2025-12-19T10:28:13.446Z",
 
155
  "body": "S\u00e3o Paulo CloudConnexa Region issue is resolved. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "minor",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2025-12-16T15:26:10.451Z",
160
  "resolved_inferred": false,
161
  "started_at": "2025-12-12T20:17:56.467Z",
 
168
  "body": "CloudConnexa Importing Profile is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "minor",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2025-11-27T15:53:24.624Z",
173
  "resolved_inferred": false,
174
  "started_at": "2025-11-27T04:12:14.726Z",
 
181
  "body": "The portals are back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "minor",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2025-11-26T23:39:52.067Z",
186
  "resolved_inferred": false,
187
  "started_at": "2025-11-26T21:58:21.223Z",
 
194
  "body": "IPsec Connector (HA/Redundant Setup) case is resolved. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2026-01-27T12:08:02.472Z",
199
  "resolved_inferred": false,
200
  "started_at": "2025-11-25T15:13:51.083Z",
 
207
  "body": "The CloudConnexa Region, Singapore, is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "minor",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2025-11-21T16:53:14.233Z",
212
  "resolved_inferred": false,
213
  "started_at": "2025-11-21T12:04:07.641Z",
 
220
  "body": "The CloudConnexa portal is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2025-11-18T18:01:40.360Z",
225
  "resolved_inferred": false,
226
  "started_at": "2025-11-18T12:06:19.695Z",
 
233
  "body": "The CloudConnexa Region, Toronto, Canada, is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "none",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2025-10-27T20:02:18.544Z",
238
  "resolved_inferred": false,
239
  "started_at": "2025-10-24T14:06:20.000Z",
 
246
  "body": "Services is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "minor",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2025-10-03T08:03:34.474Z",
251
  "resolved_inferred": false,
252
  "started_at": "2025-10-03T01:17:46.616Z",
 
259
  "body": "Brussels and London CloudConnexa Region issues is resolved. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "minor",
262
+ "last_seen": "2026-09-04T14:19:03Z",
263
  "resolved_at": "2025-10-09T15:36:45.998Z",
264
  "resolved_inferred": false,
265
  "started_at": "2025-10-02T11:11:26.000Z",
 
272
  "body": "CloudConnexa Portal is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "major",
275
+ "last_seen": "2026-09-04T14:19:03Z",
276
  "resolved_at": "2025-09-24T14:21:55.268Z",
277
  "resolved_inferred": false,
278
  "started_at": "2025-09-24T09:49:54.120Z",
 
285
  "body": "The CloudConnexa London Region for IPsec is back up and running. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "minor",
288
+ "last_seen": "2026-09-04T14:19:03Z",
289
  "resolved_at": "2025-09-11T07:38:11.386Z",
290
  "resolved_inferred": false,
291
  "started_at": "2025-09-10T12:08:08.366Z",
 
298
  "body": "Columbus CloudConnexa region issue is resolved. If you continue to experience any troubles, reach out to Support. Thank you for your patience.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "minor",
301
+ "last_seen": "2026-09-04T14:19:03Z",
302
  "resolved_at": "2025-08-20T12:19:18.793Z",
303
  "resolved_inferred": false,
304
  "started_at": "2025-08-20T10:57:20.478Z",
api/v/opswat.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "opswat",
4
  "platform": "statuspage",
5
  "status_url": "https://trust.opswat.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-09-03T10:06:29.870Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-03T09:53:10.368Z",
@@ -25,7 +25,7 @@
25
  "body": "Archive file processing will currently be limited to a maximum of 1,000 files per archive.\n\nThis temporary limitation has been implemented to help maintain service stability and consistent processing performance. Archives containing more than 1,000 files will not be fully processed.\n\nOur team is actively working to restore normal archive processing capacity. We appreciate your patience and understanding and will provide an update when the limitation has been removed.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "none",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-08-24T01:00:00.000Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-24T00:33:35.902Z",
@@ -38,7 +38,7 @@
38
  "body": "We have resolved the underlying issues that were causing extended scan times and scan failures due to infrastructure limitations. Service has been fully restored, and we apologize for any inconvenience caused by this outage.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "critical",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-08-17T18:53:02.453Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-08-17T14:21:16.242Z",
@@ -51,7 +51,7 @@
51
  "body": "We have resolved the underlying infrastructure issues that were causing delays and failures in cloud email scanning. Email scanning services have been fully restored and are operating normally. We apologize for any inconvenience caused by this outage.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "critical",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-08-17T18:55:33.264Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-08-17T14:15:54.000Z",
@@ -64,7 +64,7 @@
64
  "body": "Affected period: July 29, 2026, 06:00 UTC to July 30, 2026, 22:19 UTC\n \nBetween July 29 at 06:00 UTC and July 30 at 22:19 UTC, MetaDefender Cloud experienced a performance degradation affecting a small percentage of file submissions. Affected submissions remained In Progress longer than expected and were ultimately returned with an Aborted status. All other submissions processed normally.\n \nRoot cause: a configuration mismatch during the rollout of two new anti-malware engines caused scan-progress tracking to fail for a small number of submissions.\n \nResolution: the affected engines were removed from production scan profiles on July 30, and full recovery was verified at 22:30 UTC. Both engines will remain disabled until a permanent fix is deployed and validated. Their temporary removal does not reduce detection coverage. The permanent fix is being rolled out across all regions and is expected to complete by August 3, 2026.\n \nIf a submission returned an Aborted status during the affected period, it can be safely resubmitted and will process normally. For help identifying affected submissions, contact OPSWAT Support.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "none",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-07-29T10:00:00.000Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-07-29T10:00:00.000Z",
@@ -77,7 +77,7 @@
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-07-06T03:57:17.760Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-07-06T03:36:48.419Z",
@@ -90,7 +90,7 @@
90
  "body": "We have resolved the issue affecting MetaDefender Cloud Email Security- US.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "major",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-05-21T09:13:45.144Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-05-21T09:08:06.421Z",
@@ -103,7 +103,7 @@
103
  "body": "We have resolved the degraded performance issue.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-05-18T09:57:21.824Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-05-18T09:50:33.672Z",
@@ -116,7 +116,7 @@
116
  "body": "We have resolved this issue by disabling certain file types for this engine.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-05-05T13:00:27.534Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-05-05T07:06:43.916Z",
@@ -129,7 +129,7 @@
129
  "body": "We have resolved the issues affecting the India region.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-04-23T14:25:19.890Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-04-23T13:17:07.931Z",
@@ -142,7 +142,7 @@
142
  "body": "This incident has been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "critical",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2026-04-23T09:41:08.645Z",
147
  "resolved_inferred": false,
148
  "started_at": "2026-04-23T09:15:34.145Z",
@@ -155,7 +155,7 @@
155
  "body": "We have resolved the issue with our login service. Sorry for any inconvenience.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "critical",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2026-04-22T16:13:40.561Z",
160
  "resolved_inferred": false,
161
  "started_at": "2026-04-22T15:59:30.000Z",
@@ -168,7 +168,7 @@
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "minor",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2026-03-31T08:41:33.491Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-03-31T07:28:40.233Z",
@@ -181,7 +181,7 @@
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "none",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2026-03-18T09:11:57.502Z",
186
  "resolved_inferred": false,
187
  "started_at": "2026-03-18T08:45:10.050Z",
@@ -194,7 +194,7 @@
194
  "body": "During a planned system upgrade affecting several backend services, the MDCES user interface (UI) experienced a brief interruption starting at 8:30 AM UTC on March 18, 2026.\nThe MDCES UI was fully restored at 8:52 AM UTC, and all systems are now operating normally.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "none",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2026-03-18T08:30:00.000Z",
199
  "resolved_inferred": false,
200
  "started_at": "2026-03-18T01:30:00.000Z",
@@ -207,7 +207,7 @@
207
  "body": "This incident has been resolved.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "critical",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2026-03-16T23:15:20.219Z",
212
  "resolved_inferred": false,
213
  "started_at": "2026-03-16T22:26:04.454Z",
@@ -220,7 +220,7 @@
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2026-02-11T11:02:36.437Z",
225
  "resolved_inferred": false,
226
  "started_at": "2026-02-11T09:40:21.342Z",
@@ -233,7 +233,7 @@
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "minor",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2026-02-10T08:28:43.483Z",
238
  "resolved_inferred": false,
239
  "started_at": "2026-02-10T07:31:29.020Z",
@@ -246,7 +246,7 @@
246
  "body": "This incident has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2026-02-03T13:12:26.416Z",
251
  "resolved_inferred": false,
252
  "started_at": "2026-02-03T11:18:55.882Z",
@@ -259,7 +259,7 @@
259
  "body": "This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "minor",
262
- "last_seen": "2026-09-04T12:24:18Z",
263
  "resolved_at": "2026-01-23T06:38:52.593Z",
264
  "resolved_inferred": false,
265
  "started_at": "2026-01-22T20:23:56.305Z",
@@ -272,7 +272,7 @@
272
  "body": "The degraded performance in EU MetaDefender Cloud has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "minor",
275
- "last_seen": "2026-09-04T12:24:18Z",
276
  "resolved_at": "2026-01-13T16:16:17.200Z",
277
  "resolved_inferred": false,
278
  "started_at": "2026-01-13T15:43:04.801Z",
@@ -285,7 +285,7 @@
285
  "body": "We have resolved this issue. We apologize for any inconvenience.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "major",
288
- "last_seen": "2026-09-04T12:24:18Z",
289
  "resolved_at": "2025-12-11T16:42:48.369Z",
290
  "resolved_inferred": false,
291
  "started_at": "2025-12-11T15:07:40.432Z",
@@ -298,7 +298,7 @@
298
  "body": "This incident has been resolved. We apologize for any inconvenience caused by these issues.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "critical",
301
- "last_seen": "2026-09-04T12:24:18Z",
302
  "resolved_at": "2025-12-11T13:42:14.019Z",
303
  "resolved_inferred": false,
304
  "started_at": "2025-12-11T12:10:16.649Z",
@@ -311,7 +311,7 @@
311
  "body": "This incident has been resolved.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "minor",
314
- "last_seen": "2026-09-04T12:24:18Z",
315
  "resolved_at": "2025-12-03T08:30:00.000Z",
316
  "resolved_inferred": false,
317
  "started_at": "2025-12-03T08:30:00.000Z",
@@ -324,7 +324,7 @@
324
  "body": "This incident has been resolved.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "major",
327
- "last_seen": "2026-09-04T12:24:18Z",
328
  "resolved_at": "2025-11-25T04:05:40.453Z",
329
  "resolved_inferred": false,
330
  "started_at": "2025-11-25T03:20:50.015Z",
@@ -337,7 +337,7 @@
337
  "body": "This incident has been resolved.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "minor",
340
- "last_seen": "2026-09-04T12:24:18Z",
341
  "resolved_at": "2025-11-19T08:50:30.659Z",
342
  "resolved_inferred": false,
343
  "started_at": "2025-11-19T08:06:31.500Z",
@@ -350,7 +350,7 @@
350
  "body": "All regions have recovered.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "major",
353
- "last_seen": "2026-09-04T12:24:18Z",
354
  "resolved_at": "2025-11-18T21:39:02.072Z",
355
  "resolved_inferred": false,
356
  "started_at": "2025-11-18T18:44:01.909Z",
@@ -363,7 +363,7 @@
363
  "body": "The issue has been resolved on the Cloudflare side and Filescan.io is operational.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "critical",
366
- "last_seen": "2026-09-04T12:24:18Z",
367
  "resolved_at": "2025-11-18T14:49:29.349Z",
368
  "resolved_inferred": false,
369
  "started_at": "2025-11-18T13:42:04.166Z",
@@ -376,7 +376,7 @@
376
  "body": "This incident has been resolved.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "major",
379
- "last_seen": "2026-09-04T12:24:18Z",
380
  "resolved_at": "2025-10-31T15:38:58.046Z",
381
  "resolved_inferred": false,
382
  "started_at": "2025-10-31T14:46:00.127Z",
@@ -389,7 +389,7 @@
389
  "body": "This incident has been resolved.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "minor",
392
- "last_seen": "2026-09-04T12:24:18Z",
393
  "resolved_at": "2025-10-31T10:13:19.527Z",
394
  "resolved_inferred": false,
395
  "started_at": "2025-10-31T10:04:38.000Z",
@@ -402,7 +402,7 @@
402
  "body": "We have resolved the issue with our frontend[metadefender.opswat.com]. We apologize for any inconvenience.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "critical",
405
- "last_seen": "2026-09-04T12:24:18Z",
406
  "resolved_at": "2025-10-21T13:21:02.835Z",
407
  "resolved_inferred": false,
408
  "started_at": "2025-10-21T12:45:22.000Z",
@@ -415,7 +415,7 @@
415
  "body": "On October 20th, at approximately 2:30 PM, the AI Chatbot provider (Botpress) experienced a service interruption caused by AWS infrastructure outage.\nThis disruption impacted the availability and performance of the AI Chatbot. The provider restored and recovered by 4:12 PM on the same day.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "none",
418
- "last_seen": "2026-09-04T12:24:18Z",
419
  "resolved_at": "2025-10-21T07:30:00.000Z",
420
  "resolved_inferred": false,
421
  "started_at": "2025-10-21T07:30:00.000Z",
@@ -428,7 +428,7 @@
428
  "body": "We have resolved an issue causing increased scan times on our US region. We apologize for any inconvenience caused.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "minor",
431
- "last_seen": "2026-09-04T12:24:18Z",
432
  "resolved_at": "2025-10-16T16:30:14.098Z",
433
  "resolved_inferred": false,
434
  "started_at": "2025-10-16T15:47:35.494Z",
 
3
  "slug": "opswat",
4
  "platform": "statuspage",
5
  "status_url": "https://trust.opswat.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-09-03T10:06:29.870Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-03T09:53:10.368Z",
 
25
  "body": "Archive file processing will currently be limited to a maximum of 1,000 files per archive.\n\nThis temporary limitation has been implemented to help maintain service stability and consistent processing performance. Archives containing more than 1,000 files will not be fully processed.\n\nOur team is actively working to restore normal archive processing capacity. We appreciate your patience and understanding and will provide an update when the limitation has been removed.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "none",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-08-24T01:00:00.000Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-24T00:33:35.902Z",
 
38
  "body": "We have resolved the underlying issues that were causing extended scan times and scan failures due to infrastructure limitations. Service has been fully restored, and we apologize for any inconvenience caused by this outage.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "critical",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-08-17T18:53:02.453Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-08-17T14:21:16.242Z",
 
51
  "body": "We have resolved the underlying infrastructure issues that were causing delays and failures in cloud email scanning. Email scanning services have been fully restored and are operating normally. We apologize for any inconvenience caused by this outage.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "critical",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-08-17T18:55:33.264Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-08-17T14:15:54.000Z",
 
64
  "body": "Affected period: July 29, 2026, 06:00 UTC to July 30, 2026, 22:19 UTC\n \nBetween July 29 at 06:00 UTC and July 30 at 22:19 UTC, MetaDefender Cloud experienced a performance degradation affecting a small percentage of file submissions. Affected submissions remained In Progress longer than expected and were ultimately returned with an Aborted status. All other submissions processed normally.\n \nRoot cause: a configuration mismatch during the rollout of two new anti-malware engines caused scan-progress tracking to fail for a small number of submissions.\n \nResolution: the affected engines were removed from production scan profiles on July 30, and full recovery was verified at 22:30 UTC. Both engines will remain disabled until a permanent fix is deployed and validated. Their temporary removal does not reduce detection coverage. The permanent fix is being rolled out across all regions and is expected to complete by August 3, 2026.\n \nIf a submission returned an Aborted status during the affected period, it can be safely resubmitted and will process normally. For help identifying affected submissions, contact OPSWAT Support.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "none",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-07-29T10:00:00.000Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-07-29T10:00:00.000Z",
 
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-07-06T03:57:17.760Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-07-06T03:36:48.419Z",
 
90
  "body": "We have resolved the issue affecting MetaDefender Cloud Email Security- US.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "major",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-05-21T09:13:45.144Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-05-21T09:08:06.421Z",
 
103
  "body": "We have resolved the degraded performance issue.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-05-18T09:57:21.824Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-05-18T09:50:33.672Z",
 
116
  "body": "We have resolved this issue by disabling certain file types for this engine.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-05-05T13:00:27.534Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-05-05T07:06:43.916Z",
 
129
  "body": "We have resolved the issues affecting the India region.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-04-23T14:25:19.890Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-04-23T13:17:07.931Z",
 
142
  "body": "This incident has been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "critical",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2026-04-23T09:41:08.645Z",
147
  "resolved_inferred": false,
148
  "started_at": "2026-04-23T09:15:34.145Z",
 
155
  "body": "We have resolved the issue with our login service. Sorry for any inconvenience.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "critical",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2026-04-22T16:13:40.561Z",
160
  "resolved_inferred": false,
161
  "started_at": "2026-04-22T15:59:30.000Z",
 
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "minor",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2026-03-31T08:41:33.491Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-03-31T07:28:40.233Z",
 
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "none",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2026-03-18T09:11:57.502Z",
186
  "resolved_inferred": false,
187
  "started_at": "2026-03-18T08:45:10.050Z",
 
194
  "body": "During a planned system upgrade affecting several backend services, the MDCES user interface (UI) experienced a brief interruption starting at 8:30 AM UTC on March 18, 2026.\nThe MDCES UI was fully restored at 8:52 AM UTC, and all systems are now operating normally.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "none",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2026-03-18T08:30:00.000Z",
199
  "resolved_inferred": false,
200
  "started_at": "2026-03-18T01:30:00.000Z",
 
207
  "body": "This incident has been resolved.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "critical",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2026-03-16T23:15:20.219Z",
212
  "resolved_inferred": false,
213
  "started_at": "2026-03-16T22:26:04.454Z",
 
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2026-02-11T11:02:36.437Z",
225
  "resolved_inferred": false,
226
  "started_at": "2026-02-11T09:40:21.342Z",
 
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "minor",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2026-02-10T08:28:43.483Z",
238
  "resolved_inferred": false,
239
  "started_at": "2026-02-10T07:31:29.020Z",
 
246
  "body": "This incident has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2026-02-03T13:12:26.416Z",
251
  "resolved_inferred": false,
252
  "started_at": "2026-02-03T11:18:55.882Z",
 
259
  "body": "This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "minor",
262
+ "last_seen": "2026-09-04T14:19:03Z",
263
  "resolved_at": "2026-01-23T06:38:52.593Z",
264
  "resolved_inferred": false,
265
  "started_at": "2026-01-22T20:23:56.305Z",
 
272
  "body": "The degraded performance in EU MetaDefender Cloud has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "minor",
275
+ "last_seen": "2026-09-04T14:19:03Z",
276
  "resolved_at": "2026-01-13T16:16:17.200Z",
277
  "resolved_inferred": false,
278
  "started_at": "2026-01-13T15:43:04.801Z",
 
285
  "body": "We have resolved this issue. We apologize for any inconvenience.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "major",
288
+ "last_seen": "2026-09-04T14:19:03Z",
289
  "resolved_at": "2025-12-11T16:42:48.369Z",
290
  "resolved_inferred": false,
291
  "started_at": "2025-12-11T15:07:40.432Z",
 
298
  "body": "This incident has been resolved. We apologize for any inconvenience caused by these issues.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "critical",
301
+ "last_seen": "2026-09-04T14:19:03Z",
302
  "resolved_at": "2025-12-11T13:42:14.019Z",
303
  "resolved_inferred": false,
304
  "started_at": "2025-12-11T12:10:16.649Z",
 
311
  "body": "This incident has been resolved.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "minor",
314
+ "last_seen": "2026-09-04T14:19:03Z",
315
  "resolved_at": "2025-12-03T08:30:00.000Z",
316
  "resolved_inferred": false,
317
  "started_at": "2025-12-03T08:30:00.000Z",
 
324
  "body": "This incident has been resolved.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "major",
327
+ "last_seen": "2026-09-04T14:19:03Z",
328
  "resolved_at": "2025-11-25T04:05:40.453Z",
329
  "resolved_inferred": false,
330
  "started_at": "2025-11-25T03:20:50.015Z",
 
337
  "body": "This incident has been resolved.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "minor",
340
+ "last_seen": "2026-09-04T14:19:03Z",
341
  "resolved_at": "2025-11-19T08:50:30.659Z",
342
  "resolved_inferred": false,
343
  "started_at": "2025-11-19T08:06:31.500Z",
 
350
  "body": "All regions have recovered.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "major",
353
+ "last_seen": "2026-09-04T14:19:03Z",
354
  "resolved_at": "2025-11-18T21:39:02.072Z",
355
  "resolved_inferred": false,
356
  "started_at": "2025-11-18T18:44:01.909Z",
 
363
  "body": "The issue has been resolved on the Cloudflare side and Filescan.io is operational.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "critical",
366
+ "last_seen": "2026-09-04T14:19:03Z",
367
  "resolved_at": "2025-11-18T14:49:29.349Z",
368
  "resolved_inferred": false,
369
  "started_at": "2025-11-18T13:42:04.166Z",
 
376
  "body": "This incident has been resolved.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "major",
379
+ "last_seen": "2026-09-04T14:19:03Z",
380
  "resolved_at": "2025-10-31T15:38:58.046Z",
381
  "resolved_inferred": false,
382
  "started_at": "2025-10-31T14:46:00.127Z",
 
389
  "body": "This incident has been resolved.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "minor",
392
+ "last_seen": "2026-09-04T14:19:03Z",
393
  "resolved_at": "2025-10-31T10:13:19.527Z",
394
  "resolved_inferred": false,
395
  "started_at": "2025-10-31T10:04:38.000Z",
 
402
  "body": "We have resolved the issue with our frontend[metadefender.opswat.com]. We apologize for any inconvenience.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "critical",
405
+ "last_seen": "2026-09-04T14:19:03Z",
406
  "resolved_at": "2025-10-21T13:21:02.835Z",
407
  "resolved_inferred": false,
408
  "started_at": "2025-10-21T12:45:22.000Z",
 
415
  "body": "On October 20th, at approximately 2:30 PM, the AI Chatbot provider (Botpress) experienced a service interruption caused by AWS infrastructure outage.\nThis disruption impacted the availability and performance of the AI Chatbot. The provider restored and recovered by 4:12 PM on the same day.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "none",
418
+ "last_seen": "2026-09-04T14:19:03Z",
419
  "resolved_at": "2025-10-21T07:30:00.000Z",
420
  "resolved_inferred": false,
421
  "started_at": "2025-10-21T07:30:00.000Z",
 
428
  "body": "We have resolved an issue causing increased scan times on our US region. We apologize for any inconvenience caused.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "minor",
431
+ "last_seen": "2026-09-04T14:19:03Z",
432
  "resolved_at": "2025-10-16T16:30:14.098Z",
433
  "resolved_inferred": false,
434
  "started_at": "2025-10-16T15:47:35.494Z",
api/v/optimism.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "optimism",
4
  "platform": "instatus",
5
  "status_url": "https://status.optimism.io",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": false,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
3
  "slug": "optimism",
4
  "platform": "instatus",
5
  "status_url": "https://status.optimism.io",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": false,
9
  "first_watched": "2026-09-04T07:06:16Z",
api/v/ortto.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "ortto",
4
  "platform": "statuspage",
5
  "status_url": "https://www.orttostatus.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "The issue has been resolved and all services are operating normally. If you are still experiencing any issues, please contact our support team.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-04-10T02:03:42.974Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-04-09T05:23:12.731Z",
@@ -25,7 +25,7 @@
25
  "body": "The Knowledge Base feature should now be working again. We believe the impact was limited to our own help.ortto.com instance and should not have impacted customer instances. Please contact support if you encounter any other issues.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-03-19T02:43:20.888Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-03-19T01:00:00.000Z",
@@ -38,7 +38,7 @@
38
  "body": "We have released an update that resolves the issues affecting the Autopilot Journeys email editor and intermittent loading behavior. Resources have been reallocated, and performance has stabilized.\n\nAll functionality is now operating normally. We will continue to monitor closely to ensure continued stability. Thank you for your patience.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-01-28T00:35:56.045Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-01-27T17:55:36.453Z",
@@ -51,7 +51,7 @@
51
  "body": "The issue causing intermittent loading on the Autopilot Journeys subcomponent has been fixed. The UI should be loading normally now. Thank you for your patience while we worked on this.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-01-27T09:46:34.610Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-01-26T16:22:42.483Z",
@@ -64,7 +64,7 @@
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-01-24T13:08:41.685Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-01-23T21:40:36.202Z",
@@ -77,7 +77,7 @@
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2025-12-02T03:16:36.271Z",
82
  "resolved_inferred": false,
83
  "started_at": "2025-12-01T23:19:49.386Z",
@@ -90,7 +90,7 @@
90
  "body": "The underlying issue that caused the delays has been identified and was resolved at the time of our last update. While we continue to address the remaining fallout and follow up with impacted customers, system functionality has been restored. As a result, we are closing this incident.\n\nThank you for your patience and understanding.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2025-09-11T22:54:05.865Z",
95
  "resolved_inferred": false,
96
  "started_at": "2025-09-10T22:14:34.390Z",
@@ -103,7 +103,7 @@
103
  "body": "We have not observed any new errors, and AWS has now notified us that the issue has been fully resolved on their end. \n\nCustomers continuing to experience problems should reach out to our Support team.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "major",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2025-09-08T09:26:04.889Z",
108
  "resolved_inferred": false,
109
  "started_at": "2025-09-08T06:31:28.000Z",
 
3
  "slug": "ortto",
4
  "platform": "statuspage",
5
  "status_url": "https://www.orttostatus.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "The issue has been resolved and all services are operating normally. If you are still experiencing any issues, please contact our support team.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-04-10T02:03:42.974Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-04-09T05:23:12.731Z",
 
25
  "body": "The Knowledge Base feature should now be working again. We believe the impact was limited to our own help.ortto.com instance and should not have impacted customer instances. Please contact support if you encounter any other issues.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-03-19T02:43:20.888Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-03-19T01:00:00.000Z",
 
38
  "body": "We have released an update that resolves the issues affecting the Autopilot Journeys email editor and intermittent loading behavior. Resources have been reallocated, and performance has stabilized.\n\nAll functionality is now operating normally. We will continue to monitor closely to ensure continued stability. Thank you for your patience.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-01-28T00:35:56.045Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-01-27T17:55:36.453Z",
 
51
  "body": "The issue causing intermittent loading on the Autopilot Journeys subcomponent has been fixed. The UI should be loading normally now. Thank you for your patience while we worked on this.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-01-27T09:46:34.610Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-01-26T16:22:42.483Z",
 
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-01-24T13:08:41.685Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-01-23T21:40:36.202Z",
 
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2025-12-02T03:16:36.271Z",
82
  "resolved_inferred": false,
83
  "started_at": "2025-12-01T23:19:49.386Z",
 
90
  "body": "The underlying issue that caused the delays has been identified and was resolved at the time of our last update. While we continue to address the remaining fallout and follow up with impacted customers, system functionality has been restored. As a result, we are closing this incident.\n\nThank you for your patience and understanding.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2025-09-11T22:54:05.865Z",
95
  "resolved_inferred": false,
96
  "started_at": "2025-09-10T22:14:34.390Z",
 
103
  "body": "We have not observed any new errors, and AWS has now notified us that the issue has been fully resolved on their end. \n\nCustomers continuing to experience problems should reach out to our Support team.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "major",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2025-09-08T09:26:04.889Z",
108
  "resolved_inferred": false,
109
  "started_at": "2025-09-08T06:31:28.000Z",
api/v/osl-singapore.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "osl-singapore",
4
  "platform": "statuspage",
5
  "status_url": "https://status.osl.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
3
  "slug": "osl-singapore",
4
  "platform": "statuspage",
5
  "status_url": "https://status.osl.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
api/v/otava.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "otava",
4
  "platform": "statuspage",
5
  "status_url": "https://status.otava.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "none",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-08-13T12:36:20.090-04:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-12T12:11:07.117-04:00",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "none",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-08-12T18:55:29.099-04:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-03T12:48:31.159-04:00",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "major",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-07-28T09:12:59.297-04:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-07-26T05:54:29.000-04:00",
@@ -51,7 +51,7 @@
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-07-22T16:03:09.581-04:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-07-19T12:06:15.206-04:00",
@@ -64,7 +64,7 @@
64
  "body": "Start Time: 7/18/26 - 9:14 AM ET\n\nEnd Time: 7/18/26 - 9:14 PM ET\n\nType: Incident - Resolved\n\nService Impacting: No\n\nDescription: Utility power has been restored at the OTAVA\u00ae Mid-Michigan Data Center. As of 9:14 PM ET on Saturday, July 18, 2026, the facility has been successfully transferred back to utility power. All systems are normal and fully operational. This incident is now resolved.\n\nWe appreciate your patience during this event. If you have any questions or concerns, please contact us by logging into https://support.otava.com or calling 877-740-5028, option 3.\n\nMM1 - Mid-Michigan, MI - Building Systems",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "none",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-07-19T11:12:50.999-04:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-07-18T10:27:17.000-04:00",
@@ -77,7 +77,7 @@
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-07-17T12:23:43.862-04:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-07-17T11:05:00.930-04:00",
@@ -90,7 +90,7 @@
90
  "body": "OTAVA engineers have implemented a fix for the issue affecting scheduled Microsoft 365 backup jobs in the IN1 environment.\n\nScheduled backup jobs are now starting automatically as expected, and manual intervention is no longer required. We have confirmed that the issue has been resolved and services are operating normally. We appreciate your patience while we worked to resolve this issue.\n\nIf you have any questions or concerns regarding this incident, please get in touch with us by logging into https://support.otava.com or calling 877-740-5028, option 3.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-07-16T10:05:11.178-04:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-07-15T17:03:43.108-04:00",
@@ -103,7 +103,7 @@
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-07-27T16:01:30.437-04:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-07-15T11:16:28.683-04:00",
@@ -116,7 +116,7 @@
116
  "body": "This incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-07-14T17:23:02.983-04:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-07-13T19:34:00.914-04:00",
@@ -129,7 +129,7 @@
129
  "body": "Utility power has been restored. All systems have returned to normal operation.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "none",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-07-06T13:20:39.263-04:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-07-03T19:12:01.000-04:00",
@@ -142,7 +142,7 @@
142
  "body": "The incident has been resolved, and jobs are functioning as expected.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "major",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2026-06-30T15:38:42.814-04:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-06-30T04:56:45.005-04:00",
@@ -155,7 +155,7 @@
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "minor",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2026-07-06T11:36:29.274-04:00",
160
  "resolved_inferred": false,
161
  "started_at": "2026-06-29T13:15:00.000-04:00",
@@ -168,7 +168,7 @@
168
  "body": "The ISP has confirmed that there was a fiber cut. The circuit has been repaired and is back in service.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "none",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2026-06-26T20:55:57.627-04:00",
173
  "resolved_inferred": false,
174
  "started_at": "2026-06-24T19:40:13.270-04:00",
@@ -181,7 +181,7 @@
181
  "body": "The circuit has been repaired and it is back in production.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "none",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2026-06-26T20:53:33.368-04:00",
186
  "resolved_inferred": false,
187
  "started_at": "2026-06-24T12:48:56.754-04:00",
@@ -194,7 +194,7 @@
194
  "body": "The fiber cut has been repaired and the Austin to Las Vegas transport link is back up.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "none",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2026-06-15T16:31:47.221-04:00",
199
  "resolved_inferred": false,
200
  "started_at": "2026-06-10T14:29:22.838-04:00",
@@ -207,7 +207,7 @@
207
  "body": "This incident has been resolved.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "critical",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2026-06-15T10:10:52.765-04:00",
212
  "resolved_inferred": false,
213
  "started_at": "2026-06-10T12:59:44.468-04:00",
@@ -220,7 +220,7 @@
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2026-06-19T10:16:50.319-04:00",
225
  "resolved_inferred": false,
226
  "started_at": "2026-06-05T15:20:48.662-04:00",
@@ -233,7 +233,7 @@
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2026-06-04T08:52:09.120-04:00",
238
  "resolved_inferred": false,
239
  "started_at": "2026-06-03T17:29:54.566-04:00",
@@ -246,7 +246,7 @@
246
  "body": "This incident has been resolved. If you have any questions or concerns regarding your cloud connect backups or replications please contact us by logging into https://support.otava.com or calling 877-740-5028, option 3.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2026-06-02T09:07:32.030-04:00",
251
  "resolved_inferred": false,
252
  "started_at": "2026-05-27T10:39:18.556-04:00",
@@ -259,7 +259,7 @@
259
  "body": "This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "minor",
262
- "last_seen": "2026-09-04T12:24:18Z",
263
  "resolved_at": "2026-05-27T14:30:13.185-04:00",
264
  "resolved_inferred": false,
265
  "started_at": "2026-05-27T09:25:56.713-04:00",
@@ -272,7 +272,7 @@
272
  "body": "This incident has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "minor",
275
- "last_seen": "2026-09-04T12:24:18Z",
276
  "resolved_at": "2026-05-27T10:30:16.963-04:00",
277
  "resolved_inferred": false,
278
  "started_at": "2026-05-20T16:36:06.186-04:00",
@@ -285,7 +285,7 @@
285
  "body": "Event: The Mid-Michigan \\(MM\\) data center experienced a Denial of Service \\(DoS\\) event impacting connectivity to the data center.\n\nStart Time: 5-13-2026, Wednesday 7:13 PM ET\n\nResolved Time: 5-18-2025 , Monday 3:40 PM ET\n\nCause: A Denial of Service \\(DoS\\) event impacted network connectivity at the Mid-Michigan site.\n\nResolution: Internet Service Provider \\(ISP\\) and OTAVA engineers implemented routing and networking configuration changes such as geoblocking, Access Control Lists \\(ACL\\) changes, black hole routing and service provider AI-Powered DoS Protection.\n\nMore information will be provided when the RCA is available.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "major",
288
- "last_seen": "2026-09-04T12:24:18Z",
289
  "resolved_at": "2026-05-18T16:21:08.480-04:00",
290
  "resolved_inferred": false,
291
  "started_at": "2026-05-13T19:49:08.000-04:00",
@@ -298,7 +298,7 @@
298
  "body": "This incident has been resolved.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "minor",
301
- "last_seen": "2026-09-04T12:24:18Z",
302
  "resolved_at": "2026-04-22T12:31:22.932-04:00",
303
  "resolved_inferred": false,
304
  "started_at": "2026-04-22T09:59:23.050-04:00",
@@ -311,7 +311,7 @@
311
  "body": "This incident has been resolved.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "major",
314
- "last_seen": "2026-09-04T12:24:18Z",
315
  "resolved_at": "2026-04-15T15:35:06.296-04:00",
316
  "resolved_inferred": false,
317
  "started_at": "2026-04-15T14:56:06.393-04:00",
@@ -324,7 +324,7 @@
324
  "body": "The incident has been resolved. You may need to upgrade your Veeam Explorers to the latest version, if you have not. Please open an OTAVA ticket if you need any assistance.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "major",
327
- "last_seen": "2026-09-04T12:24:18Z",
328
  "resolved_at": "2026-04-10T10:29:33.051-04:00",
329
  "resolved_inferred": false,
330
  "started_at": "2026-04-07T11:15:35.012-04:00",
@@ -337,7 +337,7 @@
337
  "body": "This incident has been resolved.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "major",
340
- "last_seen": "2026-09-04T12:24:18Z",
341
  "resolved_at": "2026-03-20T20:24:38.460-04:00",
342
  "resolved_inferred": false,
343
  "started_at": "2026-03-20T09:30:19.769-04:00",
@@ -350,7 +350,7 @@
350
  "body": "This incident has been resolved.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "major",
353
- "last_seen": "2026-09-04T12:24:18Z",
354
  "resolved_at": "2026-03-19T03:54:57.875-04:00",
355
  "resolved_inferred": false,
356
  "started_at": "2026-03-18T06:39:35.871-04:00",
@@ -363,7 +363,7 @@
363
  "body": "Commercial utility power has been restored at the MD1 \u2013 Metro Detroit data center, and all systems have returned to normal operations. The facility is stable, and no further impact is expected.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "none",
366
- "last_seen": "2026-09-04T12:24:18Z",
367
  "resolved_at": "2026-03-15T09:26:09.907-04:00",
368
  "resolved_inferred": false,
369
  "started_at": "2026-03-13T13:29:54.279-04:00",
@@ -376,7 +376,7 @@
376
  "body": "This incident has been resolved.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "major",
379
- "last_seen": "2026-09-04T12:24:18Z",
380
  "resolved_at": "2026-02-18T09:45:11.399-05:00",
381
  "resolved_inferred": false,
382
  "started_at": "2026-01-26T18:21:11.375-05:00",
@@ -389,7 +389,7 @@
389
  "body": "This incident has been resolved.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "major",
392
- "last_seen": "2026-09-04T12:24:18Z",
393
  "resolved_at": "2026-02-02T02:45:04.735-05:00",
394
  "resolved_inferred": false,
395
  "started_at": "2026-01-25T13:35:46.867-05:00",
@@ -402,7 +402,7 @@
402
  "body": "OTAVA\u00ae engineers have determined the cause of the disruption and are working to resolve it. OTAVA will provide updates as they become available.\n\nImpact: Some OCB Veeam jobs for AU vCloud tenants may fail.\n\nIf you have any questions or concerns regarding your backups, please contact us by logging into https://support.otava.com or by emailing support@otava.com.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "minor",
405
- "last_seen": "2026-09-04T12:24:18Z",
406
  "resolved_at": "2026-01-24T22:30:00.000-05:00",
407
  "resolved_inferred": false,
408
  "started_at": "2026-01-24T22:30:00.000-05:00",
@@ -415,7 +415,7 @@
415
  "body": "The issue has been resolved and all services are operating normally. The corrective actions remain in place, and continued monitoring confirms system stability. No further impact is expected at this time.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "minor",
418
- "last_seen": "2026-09-04T12:24:18Z",
419
  "resolved_at": "2026-01-27T08:20:42.560-05:00",
420
  "resolved_inferred": false,
421
  "started_at": "2026-01-20T07:21:19.021-05:00",
@@ -428,7 +428,7 @@
428
  "body": "Otava Engineers have restored functionality and all services are back online.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "minor",
431
- "last_seen": "2026-09-04T12:24:18Z",
432
  "resolved_at": "2026-02-12T16:24:34.939-05:00",
433
  "resolved_inferred": false,
434
  "started_at": "2026-01-02T16:07:58.705-05:00",
@@ -441,7 +441,7 @@
441
  "body": "This incident has been resolved.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "none",
444
- "last_seen": "2026-09-04T12:24:18Z",
445
  "resolved_at": "2025-12-18T12:52:57.644-05:00",
446
  "resolved_inferred": false,
447
  "started_at": "2025-12-17T14:24:06.922-05:00",
@@ -454,7 +454,7 @@
454
  "body": "The backup jobs in the MM1 \u2013 Flint, MI (Mid-Michigan) OTAVA Cloud Backup environment have been successful. The repository is now operating within normal capacity levels, and all affected backup jobs have resumed normal operation.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "none",
457
- "last_seen": "2026-09-04T12:24:18Z",
458
  "resolved_at": "2025-12-05T03:20:02.091-05:00",
459
  "resolved_inferred": false,
460
  "started_at": "2025-12-01T02:09:49.448-05:00",
@@ -467,7 +467,7 @@
467
  "body": "This incident has been resolved.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "critical",
470
- "last_seen": "2026-09-04T12:24:18Z",
471
  "resolved_at": "2025-12-05T16:21:46.227-05:00",
472
  "resolved_inferred": false,
473
  "started_at": "2025-11-20T11:41:36.000-05:00",
@@ -480,7 +480,7 @@
480
  "body": "This incident has been resolved.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "critical",
483
- "last_seen": "2026-09-04T12:24:18Z",
484
  "resolved_at": "2025-11-18T13:03:23.966-05:00",
485
  "resolved_inferred": false,
486
  "started_at": "2025-11-18T09:07:53.500-05:00",
@@ -493,7 +493,7 @@
493
  "body": "This incident has been resolved.",
494
  "first_seen": "2026-09-04T07:06:16Z",
495
  "impact": "minor",
496
- "last_seen": "2026-09-04T12:24:18Z",
497
  "resolved_at": "2026-01-02T16:06:37.174-05:00",
498
  "resolved_inferred": false,
499
  "started_at": "2025-10-31T11:26:19.238-04:00",
@@ -506,7 +506,7 @@
506
  "body": "This incident has been resolved.",
507
  "first_seen": "2026-09-04T07:06:16Z",
508
  "impact": "major",
509
- "last_seen": "2026-09-04T12:24:18Z",
510
  "resolved_at": "2025-10-15T17:22:15.137-04:00",
511
  "resolved_inferred": false,
512
  "started_at": "2025-10-14T17:24:38.520-04:00",
@@ -519,7 +519,7 @@
519
  "body": "This incident has been resolved.",
520
  "first_seen": "2026-09-04T07:06:16Z",
521
  "impact": "major",
522
- "last_seen": "2026-09-04T12:24:18Z",
523
  "resolved_at": "2025-10-28T10:42:53.374-04:00",
524
  "resolved_inferred": false,
525
  "started_at": "2025-10-14T02:49:22.990-04:00",
@@ -532,7 +532,7 @@
532
  "body": "This incident has been resolved.",
533
  "first_seen": "2026-09-04T07:06:16Z",
534
  "impact": "major",
535
- "last_seen": "2026-09-04T12:24:18Z",
536
  "resolved_at": "2025-10-13T16:46:31.096-04:00",
537
  "resolved_inferred": false,
538
  "started_at": "2025-10-10T08:00:47.163-04:00",
@@ -545,7 +545,7 @@
545
  "body": "This incident has been resolved.",
546
  "first_seen": "2026-09-04T07:06:16Z",
547
  "impact": "major",
548
- "last_seen": "2026-09-04T12:24:18Z",
549
  "resolved_at": "2025-10-06T16:00:52.093-04:00",
550
  "resolved_inferred": false,
551
  "started_at": "2025-10-06T12:01:53.036-04:00",
@@ -558,7 +558,7 @@
558
  "body": "This incident has been resolved.",
559
  "first_seen": "2026-09-04T07:06:16Z",
560
  "impact": "critical",
561
- "last_seen": "2026-09-04T12:24:18Z",
562
  "resolved_at": "2025-09-19T07:53:27.548-04:00",
563
  "resolved_inferred": false,
564
  "started_at": "2025-09-10T03:29:54.492-04:00",
@@ -571,7 +571,7 @@
571
  "body": "This incident has been resolved.",
572
  "first_seen": "2026-09-04T07:06:16Z",
573
  "impact": "critical",
574
- "last_seen": "2026-09-04T12:24:18Z",
575
  "resolved_at": "2025-08-14T15:12:53.080-04:00",
576
  "resolved_inferred": false,
577
  "started_at": "2025-08-08T08:55:18.397-04:00",
@@ -584,7 +584,7 @@
584
  "body": "This incident has been resolved.",
585
  "first_seen": "2026-09-04T07:06:16Z",
586
  "impact": "minor",
587
- "last_seen": "2026-09-04T12:24:18Z",
588
  "resolved_at": "2025-08-01T21:28:34.950-04:00",
589
  "resolved_inferred": false,
590
  "started_at": "2025-08-01T21:08:16.000-04:00",
 
3
  "slug": "otava",
4
  "platform": "statuspage",
5
  "status_url": "https://status.otava.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "none",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-08-13T12:36:20.090-04:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-12T12:11:07.117-04:00",
 
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "none",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-08-12T18:55:29.099-04:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-03T12:48:31.159-04:00",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "major",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-07-28T09:12:59.297-04:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-07-26T05:54:29.000-04:00",
 
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-07-22T16:03:09.581-04:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-07-19T12:06:15.206-04:00",
 
64
  "body": "Start Time: 7/18/26 - 9:14 AM ET\n\nEnd Time: 7/18/26 - 9:14 PM ET\n\nType: Incident - Resolved\n\nService Impacting: No\n\nDescription: Utility power has been restored at the OTAVA\u00ae Mid-Michigan Data Center. As of 9:14 PM ET on Saturday, July 18, 2026, the facility has been successfully transferred back to utility power. All systems are normal and fully operational. This incident is now resolved.\n\nWe appreciate your patience during this event. If you have any questions or concerns, please contact us by logging into https://support.otava.com or calling 877-740-5028, option 3.\n\nMM1 - Mid-Michigan, MI - Building Systems",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "none",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-07-19T11:12:50.999-04:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-07-18T10:27:17.000-04:00",
 
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-07-17T12:23:43.862-04:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-07-17T11:05:00.930-04:00",
 
90
  "body": "OTAVA engineers have implemented a fix for the issue affecting scheduled Microsoft 365 backup jobs in the IN1 environment.\n\nScheduled backup jobs are now starting automatically as expected, and manual intervention is no longer required. We have confirmed that the issue has been resolved and services are operating normally. We appreciate your patience while we worked to resolve this issue.\n\nIf you have any questions or concerns regarding this incident, please get in touch with us by logging into https://support.otava.com or calling 877-740-5028, option 3.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-07-16T10:05:11.178-04:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-07-15T17:03:43.108-04:00",
 
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-07-27T16:01:30.437-04:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-07-15T11:16:28.683-04:00",
 
116
  "body": "This incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-07-14T17:23:02.983-04:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-07-13T19:34:00.914-04:00",
 
129
  "body": "Utility power has been restored. All systems have returned to normal operation.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "none",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-07-06T13:20:39.263-04:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-07-03T19:12:01.000-04:00",
 
142
  "body": "The incident has been resolved, and jobs are functioning as expected.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "major",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2026-06-30T15:38:42.814-04:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-06-30T04:56:45.005-04:00",
 
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "minor",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2026-07-06T11:36:29.274-04:00",
160
  "resolved_inferred": false,
161
  "started_at": "2026-06-29T13:15:00.000-04:00",
 
168
  "body": "The ISP has confirmed that there was a fiber cut. The circuit has been repaired and is back in service.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "none",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2026-06-26T20:55:57.627-04:00",
173
  "resolved_inferred": false,
174
  "started_at": "2026-06-24T19:40:13.270-04:00",
 
181
  "body": "The circuit has been repaired and it is back in production.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "none",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2026-06-26T20:53:33.368-04:00",
186
  "resolved_inferred": false,
187
  "started_at": "2026-06-24T12:48:56.754-04:00",
 
194
  "body": "The fiber cut has been repaired and the Austin to Las Vegas transport link is back up.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "none",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2026-06-15T16:31:47.221-04:00",
199
  "resolved_inferred": false,
200
  "started_at": "2026-06-10T14:29:22.838-04:00",
 
207
  "body": "This incident has been resolved.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "critical",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2026-06-15T10:10:52.765-04:00",
212
  "resolved_inferred": false,
213
  "started_at": "2026-06-10T12:59:44.468-04:00",
 
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2026-06-19T10:16:50.319-04:00",
225
  "resolved_inferred": false,
226
  "started_at": "2026-06-05T15:20:48.662-04:00",
 
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2026-06-04T08:52:09.120-04:00",
238
  "resolved_inferred": false,
239
  "started_at": "2026-06-03T17:29:54.566-04:00",
 
246
  "body": "This incident has been resolved. If you have any questions or concerns regarding your cloud connect backups or replications please contact us by logging into https://support.otava.com or calling 877-740-5028, option 3.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2026-06-02T09:07:32.030-04:00",
251
  "resolved_inferred": false,
252
  "started_at": "2026-05-27T10:39:18.556-04:00",
 
259
  "body": "This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "minor",
262
+ "last_seen": "2026-09-04T14:19:03Z",
263
  "resolved_at": "2026-05-27T14:30:13.185-04:00",
264
  "resolved_inferred": false,
265
  "started_at": "2026-05-27T09:25:56.713-04:00",
 
272
  "body": "This incident has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "minor",
275
+ "last_seen": "2026-09-04T14:19:03Z",
276
  "resolved_at": "2026-05-27T10:30:16.963-04:00",
277
  "resolved_inferred": false,
278
  "started_at": "2026-05-20T16:36:06.186-04:00",
 
285
  "body": "Event: The Mid-Michigan \\(MM\\) data center experienced a Denial of Service \\(DoS\\) event impacting connectivity to the data center.\n\nStart Time: 5-13-2026, Wednesday 7:13 PM ET\n\nResolved Time: 5-18-2025 , Monday 3:40 PM ET\n\nCause: A Denial of Service \\(DoS\\) event impacted network connectivity at the Mid-Michigan site.\n\nResolution: Internet Service Provider \\(ISP\\) and OTAVA engineers implemented routing and networking configuration changes such as geoblocking, Access Control Lists \\(ACL\\) changes, black hole routing and service provider AI-Powered DoS Protection.\n\nMore information will be provided when the RCA is available.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "major",
288
+ "last_seen": "2026-09-04T14:19:03Z",
289
  "resolved_at": "2026-05-18T16:21:08.480-04:00",
290
  "resolved_inferred": false,
291
  "started_at": "2026-05-13T19:49:08.000-04:00",
 
298
  "body": "This incident has been resolved.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "minor",
301
+ "last_seen": "2026-09-04T14:19:03Z",
302
  "resolved_at": "2026-04-22T12:31:22.932-04:00",
303
  "resolved_inferred": false,
304
  "started_at": "2026-04-22T09:59:23.050-04:00",
 
311
  "body": "This incident has been resolved.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "major",
314
+ "last_seen": "2026-09-04T14:19:03Z",
315
  "resolved_at": "2026-04-15T15:35:06.296-04:00",
316
  "resolved_inferred": false,
317
  "started_at": "2026-04-15T14:56:06.393-04:00",
 
324
  "body": "The incident has been resolved. You may need to upgrade your Veeam Explorers to the latest version, if you have not. Please open an OTAVA ticket if you need any assistance.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "major",
327
+ "last_seen": "2026-09-04T14:19:03Z",
328
  "resolved_at": "2026-04-10T10:29:33.051-04:00",
329
  "resolved_inferred": false,
330
  "started_at": "2026-04-07T11:15:35.012-04:00",
 
337
  "body": "This incident has been resolved.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "major",
340
+ "last_seen": "2026-09-04T14:19:03Z",
341
  "resolved_at": "2026-03-20T20:24:38.460-04:00",
342
  "resolved_inferred": false,
343
  "started_at": "2026-03-20T09:30:19.769-04:00",
 
350
  "body": "This incident has been resolved.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "major",
353
+ "last_seen": "2026-09-04T14:19:03Z",
354
  "resolved_at": "2026-03-19T03:54:57.875-04:00",
355
  "resolved_inferred": false,
356
  "started_at": "2026-03-18T06:39:35.871-04:00",
 
363
  "body": "Commercial utility power has been restored at the MD1 \u2013 Metro Detroit data center, and all systems have returned to normal operations. The facility is stable, and no further impact is expected.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "none",
366
+ "last_seen": "2026-09-04T14:19:03Z",
367
  "resolved_at": "2026-03-15T09:26:09.907-04:00",
368
  "resolved_inferred": false,
369
  "started_at": "2026-03-13T13:29:54.279-04:00",
 
376
  "body": "This incident has been resolved.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "major",
379
+ "last_seen": "2026-09-04T14:19:03Z",
380
  "resolved_at": "2026-02-18T09:45:11.399-05:00",
381
  "resolved_inferred": false,
382
  "started_at": "2026-01-26T18:21:11.375-05:00",
 
389
  "body": "This incident has been resolved.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "major",
392
+ "last_seen": "2026-09-04T14:19:03Z",
393
  "resolved_at": "2026-02-02T02:45:04.735-05:00",
394
  "resolved_inferred": false,
395
  "started_at": "2026-01-25T13:35:46.867-05:00",
 
402
  "body": "OTAVA\u00ae engineers have determined the cause of the disruption and are working to resolve it. OTAVA will provide updates as they become available.\n\nImpact: Some OCB Veeam jobs for AU vCloud tenants may fail.\n\nIf you have any questions or concerns regarding your backups, please contact us by logging into https://support.otava.com or by emailing support@otava.com.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "minor",
405
+ "last_seen": "2026-09-04T14:19:03Z",
406
  "resolved_at": "2026-01-24T22:30:00.000-05:00",
407
  "resolved_inferred": false,
408
  "started_at": "2026-01-24T22:30:00.000-05:00",
 
415
  "body": "The issue has been resolved and all services are operating normally. The corrective actions remain in place, and continued monitoring confirms system stability. No further impact is expected at this time.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "minor",
418
+ "last_seen": "2026-09-04T14:19:03Z",
419
  "resolved_at": "2026-01-27T08:20:42.560-05:00",
420
  "resolved_inferred": false,
421
  "started_at": "2026-01-20T07:21:19.021-05:00",
 
428
  "body": "Otava Engineers have restored functionality and all services are back online.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "minor",
431
+ "last_seen": "2026-09-04T14:19:03Z",
432
  "resolved_at": "2026-02-12T16:24:34.939-05:00",
433
  "resolved_inferred": false,
434
  "started_at": "2026-01-02T16:07:58.705-05:00",
 
441
  "body": "This incident has been resolved.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "none",
444
+ "last_seen": "2026-09-04T14:19:03Z",
445
  "resolved_at": "2025-12-18T12:52:57.644-05:00",
446
  "resolved_inferred": false,
447
  "started_at": "2025-12-17T14:24:06.922-05:00",
 
454
  "body": "The backup jobs in the MM1 \u2013 Flint, MI (Mid-Michigan) OTAVA Cloud Backup environment have been successful. The repository is now operating within normal capacity levels, and all affected backup jobs have resumed normal operation.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "none",
457
+ "last_seen": "2026-09-04T14:19:03Z",
458
  "resolved_at": "2025-12-05T03:20:02.091-05:00",
459
  "resolved_inferred": false,
460
  "started_at": "2025-12-01T02:09:49.448-05:00",
 
467
  "body": "This incident has been resolved.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "critical",
470
+ "last_seen": "2026-09-04T14:19:03Z",
471
  "resolved_at": "2025-12-05T16:21:46.227-05:00",
472
  "resolved_inferred": false,
473
  "started_at": "2025-11-20T11:41:36.000-05:00",
 
480
  "body": "This incident has been resolved.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "critical",
483
+ "last_seen": "2026-09-04T14:19:03Z",
484
  "resolved_at": "2025-11-18T13:03:23.966-05:00",
485
  "resolved_inferred": false,
486
  "started_at": "2025-11-18T09:07:53.500-05:00",
 
493
  "body": "This incident has been resolved.",
494
  "first_seen": "2026-09-04T07:06:16Z",
495
  "impact": "minor",
496
+ "last_seen": "2026-09-04T14:19:03Z",
497
  "resolved_at": "2026-01-02T16:06:37.174-05:00",
498
  "resolved_inferred": false,
499
  "started_at": "2025-10-31T11:26:19.238-04:00",
 
506
  "body": "This incident has been resolved.",
507
  "first_seen": "2026-09-04T07:06:16Z",
508
  "impact": "major",
509
+ "last_seen": "2026-09-04T14:19:03Z",
510
  "resolved_at": "2025-10-15T17:22:15.137-04:00",
511
  "resolved_inferred": false,
512
  "started_at": "2025-10-14T17:24:38.520-04:00",
 
519
  "body": "This incident has been resolved.",
520
  "first_seen": "2026-09-04T07:06:16Z",
521
  "impact": "major",
522
+ "last_seen": "2026-09-04T14:19:03Z",
523
  "resolved_at": "2025-10-28T10:42:53.374-04:00",
524
  "resolved_inferred": false,
525
  "started_at": "2025-10-14T02:49:22.990-04:00",
 
532
  "body": "This incident has been resolved.",
533
  "first_seen": "2026-09-04T07:06:16Z",
534
  "impact": "major",
535
+ "last_seen": "2026-09-04T14:19:03Z",
536
  "resolved_at": "2025-10-13T16:46:31.096-04:00",
537
  "resolved_inferred": false,
538
  "started_at": "2025-10-10T08:00:47.163-04:00",
 
545
  "body": "This incident has been resolved.",
546
  "first_seen": "2026-09-04T07:06:16Z",
547
  "impact": "major",
548
+ "last_seen": "2026-09-04T14:19:03Z",
549
  "resolved_at": "2025-10-06T16:00:52.093-04:00",
550
  "resolved_inferred": false,
551
  "started_at": "2025-10-06T12:01:53.036-04:00",
 
558
  "body": "This incident has been resolved.",
559
  "first_seen": "2026-09-04T07:06:16Z",
560
  "impact": "critical",
561
+ "last_seen": "2026-09-04T14:19:03Z",
562
  "resolved_at": "2025-09-19T07:53:27.548-04:00",
563
  "resolved_inferred": false,
564
  "started_at": "2025-09-10T03:29:54.492-04:00",
 
571
  "body": "This incident has been resolved.",
572
  "first_seen": "2026-09-04T07:06:16Z",
573
  "impact": "critical",
574
+ "last_seen": "2026-09-04T14:19:03Z",
575
  "resolved_at": "2025-08-14T15:12:53.080-04:00",
576
  "resolved_inferred": false,
577
  "started_at": "2025-08-08T08:55:18.397-04:00",
 
584
  "body": "This incident has been resolved.",
585
  "first_seen": "2026-09-04T07:06:16Z",
586
  "impact": "minor",
587
+ "last_seen": "2026-09-04T14:19:03Z",
588
  "resolved_at": "2025-08-01T21:28:34.950-04:00",
589
  "resolved_inferred": false,
590
  "started_at": "2025-08-01T21:08:16.000-04:00",
api/v/otoy.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "otoy",
4
  "platform": "statuspage",
5
  "status_url": "https://status.otoy.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "We have identified and corrected the problem.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2025-10-08T11:56:18.279-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2025-10-08T11:08:14.660-07:00",
@@ -25,7 +25,7 @@
25
  "body": "OctaneLive continues to operate normally, this outage will be closed out shortly.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "critical",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2025-10-03T11:34:26.072-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2025-10-03T08:42:39.165-07:00",
 
3
  "slug": "otoy",
4
  "platform": "statuspage",
5
  "status_url": "https://status.otoy.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "We have identified and corrected the problem.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2025-10-08T11:56:18.279-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2025-10-08T11:08:14.660-07:00",
 
25
  "body": "OctaneLive continues to operate normally, this outage will be closed out shortly.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "critical",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2025-10-03T11:34:26.072-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2025-10-03T08:42:39.165-07:00",
api/v/outsystems.json CHANGED
@@ -3,27 +3,29 @@
3
  "slug": "outsystems",
4
  "platform": "statuspage",
5
  "status_url": "https://status.outsystems.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "partial",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
10
  "incidents": [
11
  {
12
- "body": "We have identified an issue affecting npm audit actions during npm installations and are currently working on a fix.",
13
  "first_seen": "2026-09-04T11:14:03Z",
14
  "impact": "major",
15
- "last_seen": "2026-09-04T12:24:18Z",
 
 
16
  "started_at": "2026-09-04T11:15:06.692Z",
17
- "state": "identified",
18
  "title": "MABS Android and iOS builds timming out",
19
- "updated_at": "2026-09-04T11:15:06.781Z",
20
  "url": "https://stspg.io/c5xghzgxc8ly"
21
  },
22
  {
23
  "body": "_Between August 28th and August 31st, 2026, users in the Asia Pacific \\(Sydney\\) region were unable to use Mentor in ODC Studio. Connection attempts returned an error stating, \"Mentor couldn't connect. Please go online and try again.\" Deployed applications and other ODC Studio functionality were not affected._ \n_As part of planned regional infrastructure work, Mentor connection requests from affected environments began being sent to a new regional destination. The services needed to handle those requests had not yet been deployed there, so every connection attempt failed. The change was applied ahead of those services becoming available._ \n_The issue was detected through customer reports. Automated monitoring did not alert on it, because connection requests were being sent to a destination where the supporting service was not yet running, so no failure signals were generated for our monitoring to detect._ \n_To restore service, we reversed the configuration change on a single environment and confirmed that Mentor connected successfully, then applied the same reversal across all affected environments. We verified recovery with each of the customers who had reported the issue._ \n_To prevent recurrence, the regional infrastructure work will not resume until all dependent services are available in the region. We are strengthening the validation applied before configuration updates of this kind, so that a change cannot be made ahead of the services it depends on. We are also reviewing our monitoring so that failures of this type are detected automatically rather than through customer reports._ \n_We apologise for any disruption caused and thank you for your patience._",
24
  "first_seen": "2026-09-04T07:06:16Z",
25
  "impact": "critical",
26
- "last_seen": "2026-09-04T12:24:18Z",
27
  "resolved_at": "2026-08-31T18:00:40.904Z",
28
  "resolved_inferred": false,
29
  "started_at": "2026-08-31T15:28:49.850Z",
@@ -36,7 +38,7 @@
36
  "body": "On August 26th, between 05:16 UTC and 16:26 UTC, some ODC users experienced delays in the execution of timers. Affected timers remained pending instead of running as scheduled, and subsequent runs did not start. Users in US East / Virginia and Asia Pacific / Singapore were affected. Applications themselves remained available throughout.\n\nThe issue was caused by a recent platform update that changed how a timer's status is recorded once it has run. Under that update, a timer whose status needed to be recorded more than once in sequence failed to update correctly, leaving it pending and blocking later scheduled executions. To restore service, our team returned the affected part of the platform to its previous version, which stopped the issue recurring for affected users. A permanent correction was then developed, validated and deployed across the platform, and we confirmed that timers were executing normally before closing the incident.\n\nWe are reviewing our monitoring of timer execution so that issues of this kind are detected automatically rather than through customer reports. We apologise for any disruption caused and thank you for your patience.",
37
  "first_seen": "2026-09-04T07:06:16Z",
38
  "impact": "minor",
39
- "last_seen": "2026-09-04T12:24:18Z",
40
  "resolved_at": "2026-08-26T16:33:04.484Z",
41
  "resolved_inferred": false,
42
  "started_at": "2026-08-26T05:16:49.409Z",
@@ -49,7 +51,7 @@
49
  "body": "On August 24th, 2026, some users experienced an issue affecting application deployments in ODC Portal. Affected users intermittently saw the error message: \"An error occurred while getting the generated code from revision. \\(OS-STGC-60005\\)\".\n\nThe issue was caused by an internal scaling tool that interfered with a backend service used to prepare deployment packages, causing delays and errors for some deployment requests. We fixed the scaling configuration to restore normal behavior.\n\nTo prevent a recurrence, we are working with the provider of the automated scaling tool to correct the underlying behavior, and have put a permanent safeguard in place to stop the affected service from being mismanaged by that tool going forward.\n\nWe apologize for any disruption caused and thank you for your patience.",
50
  "first_seen": "2026-09-04T07:06:16Z",
51
  "impact": "major",
52
- "last_seen": "2026-09-04T12:24:18Z",
53
  "resolved_at": "2026-08-24T19:12:27.000Z",
54
  "resolved_inferred": false,
55
  "started_at": "2026-08-24T14:57:08.453Z",
@@ -62,7 +64,7 @@
62
  "body": "Between 20 August 9:52 UTC and 21 August 13:22 UTC, some users were unable to generate or edit applications using Mentor in the ODC Portal, and received the error OS-IDE-CONVERSATIONAL-50035. \nThe issue was caused by an outdated permission check that remained in place after a recent change to how the service communicates internally. \nWe removed the outdated check and confirmed that the Mentor App Generator App Editor recovered across the affected regions. \nWe apologise for the disruption this caused.",
63
  "first_seen": "2026-09-04T07:06:16Z",
64
  "impact": "minor",
65
- "last_seen": "2026-09-04T12:24:18Z",
66
  "resolved_at": "2026-08-21T16:20:15.691Z",
67
  "resolved_inferred": false,
68
  "started_at": "2026-08-21T10:54:59.659Z",
@@ -75,7 +77,7 @@
75
  "body": "This incident has been resolved.",
76
  "first_seen": "2026-09-04T07:06:16Z",
77
  "impact": "minor",
78
- "last_seen": "2026-09-04T12:24:18Z",
79
  "resolved_at": "2026-08-13T11:21:50.855Z",
80
  "resolved_inferred": false,
81
  "started_at": "2026-08-12T16:56:12.323Z",
@@ -88,7 +90,7 @@
88
  "body": "On August 12th, 2026, at approximately 02:56 UTC, we received our first customer report regarding an issue that affected the Application Configuration and IP Filter List features, resulting in these areas failing to load for a number of customers. Application publishing and runtime were not affected. Customers saw the error codes OS-APPC-60043 and OS-CFGC-GEN-60030. This prevented some users from completing required application configuration changes. Normal service was restored at 08:00 UTC.\n\nIt was caused by a recent update to an internal service that provides configuration data. The update unintentionally changed how requests were routed between instances of that service, so most requests for IP filter information reached an instance that could not answer them and timed out. Our team identified the faulty update and rolled it back across all environments to restore normal behavior.\n\nWe are improving our pre-release testing and monitoring so that this type of issue is caught before it reaches production, and adding monitoring coverage specifically for this failure mode.",
89
  "first_seen": "2026-09-04T07:06:16Z",
90
  "impact": "minor",
91
- "last_seen": "2026-09-04T12:24:18Z",
92
  "resolved_at": "2026-08-12T10:38:54.028Z",
93
  "resolved_inferred": false,
94
  "started_at": "2026-08-12T05:41:29.472Z",
@@ -101,7 +103,7 @@
101
  "body": "On August 10th, 2026, from 20:31 to 22:19 UTC, users in the South America / S\u00e3o Paulo region experienced errors when signing in to ODC. This prevented affected users from accessing their Production applications and also affected the ODC Portal and ODC Studio.\n\nThe issue was detected through customer reports and monitoring. Our investigation found that a fault in an internal caching component of our identity service was preventing it from issuing sign-in tokens, even though the service otherwise appeared to be running normally.\n\nTo restore service, our team restarted the affected identity service, which cleared the fault and allowed token issuance to resume. We confirmed with affected customers that sign-in and application access had returned to normal before closing the incident.\n\nWe have identified additional monitoring and preventive improvements for this component and are prioritising their rollout to help reduce the risk of similar issues recurring. We apologise for any disruption caused and thank you for your patience.",
102
  "first_seen": "2026-09-04T07:06:16Z",
103
  "impact": "major",
104
- "last_seen": "2026-09-04T12:24:18Z",
105
  "resolved_at": "2026-08-11T07:54:40.255Z",
106
  "resolved_inferred": false,
107
  "started_at": "2026-08-10T20:48:01.967Z",
@@ -114,7 +116,7 @@
114
  "body": "On July 31st, 2026, an issue affected applications running in the Development Stage in Europe Central \\(Frankfurt\\). Applications experienced extended delays \\(2\u20133 minutes\\) and timeout errors when starting up from an idle state.\n\nThe issue lasted approximately a few hours and was detected through customer reports and platform monitoring. During this time, several customers in the region reported difficulties launching their applications in the Development Stage's Runtime.\n\nOur investigation identified a memory issue in a critical component responsible for automatically scaling applications based on incoming traffic. This component was consuming excessive memory and restarting repeatedly, which prevented applications from scaling up when first accessed. Our team immediately implemented an operational workaround by increasing resource limits for this component. This mitigation immediately allowed applications to scale up as expected.\n\nIn parallel, we developed a permanent code fix to address the root cause and deployed it on August 7th. The system remained stable, with no new occurrences during and after the deployment of the permanent fix.\n\nTo prevent similar issues, OutSystems is improving how we monitor and validate infrastructure configuration to catch memory and resource issues earlier, and we are enhancing our automated scaling components to handle traffic pattern changes more gracefully.\n\nWe apologise for any disruption caused and thank you for your patience.",
115
  "first_seen": "2026-09-04T07:06:16Z",
116
  "impact": "minor",
117
- "last_seen": "2026-09-04T12:24:18Z",
118
  "resolved_at": "2026-08-07T08:34:33.760Z",
119
  "resolved_inferred": false,
120
  "started_at": "2026-07-31T08:31:58.000Z",
@@ -127,7 +129,7 @@
127
  "body": "On July 30, 2026, between 15:19 and 15:59 UTC, customers in multiple regions experienced an outage affecting access to the OutSystems ODC Portal, preventing them from logging in or accessing their development environments. The incident was caused by the addition of a custom header, which prevented requests from reaching the portal. Following the code change rollback, service was restored by 15:59 UTC. To prevent similar incidents in the future, we are implementing additional automated testing to validate configuration changes before they are deployed to production and conducting a comprehensive review of our code review and testing procedures to catch such issues earlier in the development process. We appreciate your patience during this incident and apologize for any disruption to your work.",
128
  "first_seen": "2026-09-04T07:06:16Z",
129
  "impact": "none",
130
- "last_seen": "2026-09-04T12:24:18Z",
131
  "resolved_at": "2026-07-30T18:39:10.991Z",
132
  "resolved_inferred": false,
133
  "started_at": "2026-07-30T18:39:10.882Z",
@@ -140,7 +142,7 @@
140
  "body": "On the 20th of July 2026, there was an issue with the wake-up functionality affecting Personal Editions. This occurred in all three regions \\(US East, Europe and Asia Pacific\\). \nUsers were unable to wake up their environments from hibernation. When attempting to wake up the environments, they either remained in hibernation or moved to a \"waking up\" state indefinitely, preventing access to applications. \nThis was caused by an issue in how our backend systems processed environment status updates. Due to messages being processed out of order, some environments' internal state was incorrectly reverted to 'hibernated' after they had already woken up successfully, even though the environment itself remained accessible on the backend. This caused the ODC Portal to keep showing an inaccurate 'hibernated' or 'waking up' status, and repeated wake-up attempts did not resolve it since the underlying state kept getting overwritten. \nWe identified the root cause on the 21st of July and deployed a code fix to correct the state synchronization. The fix started to be rolled out to all regions on 22nd of July and completed by the 23rd of July. All affected environments were woken up successfully. \nWe are implementing additional state verification checks to ensure the ODC Portal and backend systems remain in sync. A full technical review is underway to identify similar synchronization gaps across other features. \nWe apologize for any disruption caused and thank you for your patience.",
141
  "first_seen": "2026-09-04T07:06:16Z",
142
  "impact": "major",
143
- "last_seen": "2026-09-04T12:24:18Z",
144
  "resolved_at": "2026-07-23T09:06:28.653Z",
145
  "resolved_inferred": false,
146
  "started_at": "2026-07-21T02:13:51.671Z",
@@ -153,7 +155,7 @@
153
  "body": "This incident has been resolved. ODC Personal Editions are now\noperating normally.\nIf you have not yet done so, please access your\nPersonal Edition by clicking \"Wake Up\" in the ODC Portal.\nIf you experience any issues, our support team is available to assist.\nThank you for your patience.",
154
  "first_seen": "2026-09-04T07:06:16Z",
155
  "impact": "major",
156
- "last_seen": "2026-09-04T12:24:18Z",
157
  "resolved_at": "2026-07-20T17:37:51.191Z",
158
  "resolved_inferred": false,
159
  "started_at": "2026-07-20T11:46:15.940Z",
@@ -166,7 +168,7 @@
166
  "body": "On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.",
167
  "first_seen": "2026-09-04T07:06:16Z",
168
  "impact": "major",
169
- "last_seen": "2026-09-04T12:24:18Z",
170
  "resolved_at": "2026-06-30T18:22:41.851Z",
171
  "resolved_inferred": false,
172
  "started_at": "2026-06-30T08:56:27.789Z",
@@ -179,7 +181,7 @@
179
  "body": "On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.",
180
  "first_seen": "2026-09-04T07:06:16Z",
181
  "impact": "major",
182
- "last_seen": "2026-09-04T12:24:18Z",
183
  "resolved_at": "2026-06-29T18:07:13.000Z",
184
  "resolved_inferred": false,
185
  "started_at": "2026-06-29T04:28:44.715Z",
@@ -192,7 +194,7 @@
192
  "body": "On June 24th, an issue occurred that impacted ODC application deployments for non-administrator users across multiple regions, including Asia Pacific and Europe. Affected users experienced failures when attempting to deploy applications to higher stages and received an error during the build preparation step. Administrator accounts were not affected.\n\nThe issue was caused by a configuration change deployed on June 23rd, which introduced a technical mismatch in how permission roles were validated within the build pipeline, preventing non-admin users from initiating deployments. The engineering team identified the root cause and reversed the change.\n\nDeployments are now functioning normally for all affected users. We are conducting a post-incident review to prevent similar issues from occurring in the future.",
193
  "first_seen": "2026-09-04T07:06:16Z",
194
  "impact": "minor",
195
- "last_seen": "2026-09-04T12:24:18Z",
196
  "resolved_at": "2026-06-25T12:31:39.814Z",
197
  "resolved_inferred": false,
198
  "started_at": "2026-06-25T08:44:37.103Z",
@@ -205,7 +207,7 @@
205
  "body": "On June 22nd, an incident affected ODC users in the US East \\(N. Virginia\\) region. Users were unable to access any applications in the Development stage, receiving an \"Upstream Request Timeout\" error. Production and Test stages, as well as all other regions, were unaffected.\n\nThe incident was caused by a platform configuration change that prevented the component responsible for starting idle Development-stage applications on demand from functioning. As a result, when a request arrived, the application failed to start, causing the connection to time out at the gateway.\n\nThe issue was resolved by reverting the configuration change. The component fully recovered, app startup resumed, and normal service operation was verified.",
206
  "first_seen": "2026-09-04T07:06:16Z",
207
  "impact": "minor",
208
- "last_seen": "2026-09-04T12:24:18Z",
209
  "resolved_at": "2026-06-22T12:42:49.313Z",
210
  "resolved_inferred": false,
211
  "started_at": "2026-06-22T11:37:51.203Z",
@@ -218,7 +220,7 @@
218
  "body": "On May 22, 2026, we deployed an update intended to improve internal diagnostics. This update added automatic comments to generated SQL statements. In a specific edge case, where count-based queries were used inside nested SQL statements, these added comments disrupted the structure of the query and caused it to fail. Affected applications returned runtime errors and certain database queries could not complete successfully. \nAfter deploying a fix for this, services were restored and all affected queries are now functioning normally. \nWe appreciate your patience while this was being resolved and remain committed to continuously improving the stability and reliability of the platform.",
219
  "first_seen": "2026-09-04T07:06:16Z",
220
  "impact": "minor",
221
- "last_seen": "2026-09-04T12:24:18Z",
222
  "resolved_at": "2026-05-25T13:37:01.699Z",
223
  "resolved_inferred": false,
224
  "started_at": "2026-05-22T14:58:38.280Z",
@@ -231,7 +233,7 @@
231
  "body": "On May 8, 2026, at 12:03 AM UTC, ODC and O11 Personal Environments in the N. Virginia region experienced a service disruption caused by an AWS infrastructure event affecting a single Availability Zone. The disruption was related to an external power and cooling issue that impacted the availability of underlying AWS services. \nCustomers experienced service unavailability, including issues with logging in and publishing applications.The impact was limited to O11 Personal Environments and a small subset of users, while impact on ODC remained contained. \nAs AWS services recovered, many OutSystems environments resumed normal operation automatically. Some environments required additional recovery actions to fully restore service availability. \nFor ODC, the incident was fully resolved on May 9, 2026, at 3:30 AM UTC. Recovery efforts for O11 Personal Environments continued afterward due to the additional complexity of restoring affected environments. \nAll services are now operating as expected, and no user action is required.",
232
  "first_seen": "2026-09-04T07:06:16Z",
233
  "impact": "major",
234
- "last_seen": "2026-09-04T12:24:18Z",
235
  "resolved_at": "2026-05-11T16:12:05.338Z",
236
  "resolved_inferred": false,
237
  "started_at": "2026-05-08T11:56:03.115Z",
@@ -244,7 +246,7 @@
244
  "body": "This incident has been resolved.",
245
  "first_seen": "2026-09-04T07:06:16Z",
246
  "impact": "major",
247
- "last_seen": "2026-09-04T12:24:18Z",
248
  "resolved_at": "2026-04-21T10:19:47.188Z",
249
  "resolved_inferred": false,
250
  "started_at": "2026-04-21T02:36:07.374Z",
@@ -257,7 +259,7 @@
257
  "body": "On April 13,2026 between 1:13 and 3:07 AM UTC, an incident occurred that prevented users from logging in to the ODC Portal across multiple regions. The issue was caused by a deployment of a Identity Service that required a database schema change that had not yet been applied, resulting in authentication failures.\n\nService was restored after the team initiated a rollback to the previous stable version. Validation confirmed that login functionality was restored for all users. \n\nThe incident is fully resolved, and all services are operating as expected.",
258
  "first_seen": "2026-09-04T07:06:16Z",
259
  "impact": "critical",
260
- "last_seen": "2026-09-04T12:24:18Z",
261
  "resolved_at": "2026-04-13T03:30:32.085Z",
262
  "resolved_inferred": false,
263
  "started_at": "2026-04-13T02:24:21.692Z",
@@ -270,7 +272,7 @@
270
  "body": "The issues affecting our services have been resolved, and all systems are now operating normally. We apologize for any disruption this may have caused to your workflows.",
271
  "first_seen": "2026-09-04T07:06:16Z",
272
  "impact": "critical",
273
- "last_seen": "2026-09-04T12:24:18Z",
274
  "resolved_at": "2026-03-30T11:22:22.790Z",
275
  "resolved_inferred": false,
276
  "started_at": "2026-03-29T01:06:32.583Z",
@@ -283,7 +285,7 @@
283
  "body": "On March 19th, 2026, at approximately 06:43 UTC, an issue was identified affecting ODC, where some users were unable to complete the login process for the ODC Portal and ODC Studio when using external Identity Providers. Affected users encountered an error message stating \"Email verification not supported\" or were blocked from accessing their accounts because the system could not verify their email addresses via the external provider's claims.\n\nThe incident was caused by a configuration change intended to strictly enforce email verification from external providers. This change inadvertently bypassed a native fallback verification process that certain users relied upon when their external providers did not share specific verification data.\n\nThe issue was resolved by 11:00 UTC on March 19th following a rollback to the previous service versions. To prevent recurrence, future updates to this functionality will be implemented via a gradual rollout plan, including additional validation steps to ensure all identity provider configurations are fully supported.",
284
  "first_seen": "2026-09-04T07:06:16Z",
285
  "impact": "major",
286
- "last_seen": "2026-09-04T12:24:18Z",
287
  "resolved_at": "2026-03-19T11:32:05.121Z",
288
  "resolved_inferred": false,
289
  "started_at": "2026-03-19T09:35:30.445Z",
@@ -296,7 +298,7 @@
296
  "body": "On March 4th, 2026, between 2:39 am and 10:29 am UTC, ODC experienced an incident that prevented users from accessing the App Detail screen and performing app configurations across all stages. The runtime of existing applications was not affected by this issue. \nThe root cause was a subscription validation misalignment between internal APIs and ODC Portal, which resulted in errors for customers without the ODC Sentry add-on. \nTo prevent future occurrences, we are updating ODC Portal to verify subscription status in alignment with these APIs and improving UI error handling to ensure failures like this do not obstruct the overall page experience.",
297
  "first_seen": "2026-09-04T07:06:16Z",
298
  "impact": "major",
299
- "last_seen": "2026-09-04T12:24:18Z",
300
  "resolved_at": "2026-03-04T10:41:33.282Z",
301
  "resolved_inferred": false,
302
  "started_at": "2026-03-04T09:09:44.870Z",
@@ -309,7 +311,7 @@
309
  "body": "All customers impacted by this incident have been contacted and supported individually. While the Middle East region continues to be affected by the ongoing geopolitical situation and AWS continues to report the region as impacted, OutSystems has completed its direct response to every affected organization. \nThe affected services remain flagged as a major outage while these conditions persist. Customers who need further assistance can contact OutSystems Support by raising a new ticket or continuing their existing case through Support Services.",
310
  "first_seen": "2026-09-04T07:06:16Z",
311
  "impact": "critical",
312
- "last_seen": "2026-09-04T12:24:18Z",
313
  "resolved_at": "2026-07-03T14:41:51.440Z",
314
  "resolved_inferred": false,
315
  "started_at": "2026-03-01T16:33:04.355Z",
@@ -322,7 +324,7 @@
322
  "body": "On January 30th, several ODC customers experienced intermittent issues where the username attribute was missing data from the User entity within applications. \nThe cause was identified as a bug in a recent release of an identity component. This issue prevented specific user and identity provider data from correctly populating the Username Attribute. \nThe incident was resolved by rolling back the affected release. A corrected version has since been deployed to ensure consistent data availability and prevent future occurrences.",
323
  "first_seen": "2026-09-04T07:06:16Z",
324
  "impact": "major",
325
- "last_seen": "2026-09-04T12:24:18Z",
326
  "resolved_at": "2026-01-30T12:43:09.769Z",
327
  "resolved_inferred": false,
328
  "started_at": "2026-01-29T20:00:44.115Z",
@@ -335,7 +337,7 @@
335
  "body": "On January 27th, we experienced a service disruption in Mentor affecting APAC and EMEA regions. Users encountered elevated error rates and a loss of functionality for Mentor features.\n\nThe incident was triggered by a third-party service outage, which hosts the models supporting our Data & AI services. While a fallback system was in place, it also became unavailable during the outage. Furthermore, the impact of the external service disruption also prevented our team from implementing a manual configuration fix immediately.\n\nWe are also working toward an automated fallback mechanism to minimize the need for manual intervention. Additionally, we are implementing agent-level fallbacks to different models at the product level.",
336
  "first_seen": "2026-09-04T07:06:16Z",
337
  "impact": "major",
338
- "last_seen": "2026-09-04T12:24:18Z",
339
  "resolved_at": "2026-01-27T18:20:48.471Z",
340
  "resolved_inferred": false,
341
  "started_at": "2026-01-27T12:53:02.416Z",
@@ -348,7 +350,7 @@
348
  "body": "On January 22nd, between 15:00 UTC and 17:00 UTC, an incident affected ODC in the Europe \\(Frankfurt\\) region. Users experienced issues with One-Click Publish, specifically resulting in build timeouts and publish failures. \n\nThe issue was caused by a communication failure between the internal queuing system and the Build Service, which prevented build processes from completing. \n\nOur team resolved the incident by restarting the Build Service and restoring communication. Normal service has been restored, and we are evaluating measures to improve system resilience moving forward.",
349
  "first_seen": "2026-09-04T07:06:16Z",
350
  "impact": "major",
351
- "last_seen": "2026-09-04T12:24:18Z",
352
  "resolved_at": "2026-01-22T16:52:18.961Z",
353
  "resolved_inferred": false,
354
  "started_at": "2026-01-22T15:29:09.888Z",
@@ -361,7 +363,7 @@
361
  "body": "On January 16th, a service change related to an ongoing migration caused a temporary issue where customers were unable to log in using their custom domains. Our engineering team immediately identified the cause and implemented a mitigation to resolve the issue quickly by temporarily disabling the custom domain redirection feature. A controlled restart of system deployments was performed to expedite this fix.\n\nTo ensure stability and prevent recurrence, a technical recommendation has been made to enhance the system. This improvement will increase resilience to future updates and configuration changes, helping maintain continuous operation without service interruptions.",
362
  "first_seen": "2026-09-04T07:06:16Z",
363
  "impact": "major",
364
- "last_seen": "2026-09-04T12:24:18Z",
365
  "resolved_at": "2026-01-16T14:35:08.339Z",
366
  "resolved_inferred": false,
367
  "started_at": "2026-01-16T10:13:39.978Z",
@@ -374,7 +376,7 @@
374
  "body": "On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.\n\nThe incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.\n\nTo resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.\n\nTo prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.",
375
  "first_seen": "2026-09-04T07:06:16Z",
376
  "impact": "major",
377
- "last_seen": "2026-09-04T12:24:18Z",
378
  "resolved_at": "2025-12-08T15:46:04.126Z",
379
  "resolved_inferred": false,
380
  "started_at": "2025-12-08T13:36:21.621Z",
@@ -387,7 +389,7 @@
387
  "body": "On December 8th, we experienced an issue that affected application publishing. This resulted in users being unable to publish any applications in the Development stage across all regions, encountering the error code OS-DPL-40802 \\(Deployment timeout\\).\n\nThe root cause of the incident was a new version of an internal service that was deployed around the same time the problem started. This new version contained changes that caused application deployments to fail.\n\nThe issue was resolved by reverting the internal service to the previous stable version.",
388
  "first_seen": "2026-09-04T07:06:16Z",
389
  "impact": "major",
390
- "last_seen": "2026-09-04T12:24:18Z",
391
  "resolved_at": "2025-12-08T11:12:45.118Z",
392
  "resolved_inferred": false,
393
  "started_at": "2025-12-08T10:15:04.809Z",
@@ -400,7 +402,7 @@
400
  "body": "On November 26th, an issue was experienced affecting Personal Editions users, resulting in users seeing a \u201cno permissions\u201d page and being unable to use their Personal Edition environments. Normal service was restored at 21:00 UTC.\n\nThe incident was caused by the reconfiguration step used to fix an earlier issue. This step correctly re-applied the Identity Provider \\(IdP\\) but also unintentionally made the affected Personal Editions environments available for re-assignment. As a result, many of the previously fixed Personal Editions were re-assigned to \"second\" users who were created without any permissions upon first login, leading to the \u201cno permissions\u201d screen.\n\nTo prevent new occurrences, all Personal Editions environments created during the faulty period that had gone through the reconfiguration were discarded. Impacted users were proactively informed and instructed to request a new Personal Edition.",
401
  "first_seen": "2026-09-04T07:06:16Z",
402
  "impact": "major",
403
- "last_seen": "2026-09-04T12:24:18Z",
404
  "resolved_at": "2025-11-26T21:01:14.873Z",
405
  "resolved_inferred": false,
406
  "started_at": "2025-11-26T10:07:52.000Z",
@@ -413,7 +415,7 @@
413
  "body": "On November 25th, around 11:15 UTC, we experienced an issue affecting Personal Editions, resulting in users being unable to log in and consistently seeing the error \u201cIncorrect username or password \\(OS-UAUC-60004\\)\u201d despite using valid credentials in the regions of US East \\(Ohio\\), Europe \\(Ireland\\), and Asia Pacific \\(Singapore\\). Normal service was restored by approximately 17:00 UTC the same day.\n\nThe incident was caused by an issue in provisioning that led Personal Editions to not have the built-in community provider configured as an Identity Provider. This resulted in the login failures when users attempted to access their Personal Editions.\n\nTo prevent new occurrences, the provisioning logic was updated to treat a similar empty response as an error, triggering an internal alert and preventing affected environments from being handed out as ready-to-use. Additionally, a targeted reconfiguration job was run to correctly apply the required identity provider to all impacted Personal Editions, which restored normal login functionality",
414
  "first_seen": "2026-09-04T07:06:16Z",
415
  "impact": "major",
416
- "last_seen": "2026-09-04T12:24:18Z",
417
  "resolved_at": "2025-11-25T17:06:54.578Z",
418
  "resolved_inferred": false,
419
  "started_at": "2025-11-25T12:37:30.726Z",
@@ -426,7 +428,7 @@
426
  "body": "On November 24, 2025, a new version of our deployment service was released, including an internal library update intended to optimize the processing of external libraries. This update inadvertently caused a logic error that made deployments hang during certain operations, leading to intermittent timeouts for customers deploying external libraries or applications that depend on them. Not all deployments were affected, and the impact varied by region and library volume. We immediately reverted the service to the previous stable version, restoring normal deployment operations. \n\nWe are working to correct the issue in the internal library and will reintroduce the optimization after thorough validation to prevent future disruptions. \n\nWe apologize for the inconvenience and appreciate your patience.",
427
  "first_seen": "2026-09-04T07:06:16Z",
428
  "impact": "major",
429
- "last_seen": "2026-09-04T12:24:18Z",
430
  "resolved_at": "2025-11-24T12:09:07.383Z",
431
  "resolved_inferred": false,
432
  "started_at": "2025-11-24T11:46:09.029Z",
@@ -439,7 +441,7 @@
439
  "body": "On November 18th, we experienced an issue that prevented users with Personal Editions from accessing the ODC Portal login page. Customers who were affected saw the error message: \"Something unexpected happened during login. Please try logging in again using a new tab or a different browser\". Normal service was restored at 11:09 AM UTC.\n\nThe incident was caused by a recent system update that introduced an error in how login data was processed. Full access was restored after we reverted the affected system component to its previous version. We apologize for the inconvenience this caused.",
440
  "first_seen": "2026-09-04T07:06:16Z",
441
  "impact": "critical",
442
- "last_seen": "2026-09-04T12:24:18Z",
443
  "resolved_at": "2025-11-18T11:28:20.067Z",
444
  "resolved_inferred": false,
445
  "started_at": "2025-11-18T09:56:52.556Z",
@@ -452,7 +454,7 @@
452
  "body": "A platform-wide issue was identified where log messages generated within successful Timers were inconsistently or completely missing from the monitoring interface. \nThe root cause was a technical race condition during a critical component startup, which prevented logs from reaching the central logging system. Engineering team developed and deployed an update that resolved the issue, and extensive monitoring has confirmed the platform is now stable, with all Timer-originated log entries appearing correctly.",
453
  "first_seen": "2026-09-04T07:06:16Z",
454
  "impact": "minor",
455
- "last_seen": "2026-09-04T12:24:18Z",
456
  "resolved_at": "2025-11-17T17:45:47.025Z",
457
  "resolved_inferred": false,
458
  "started_at": "2025-11-14T14:26:56.766Z",
@@ -465,7 +467,7 @@
465
  "body": "Customers experienced intermittent service issues with core operations, including deployments and authentication, between 2:58 and 10:40 UTC. \nThe disruption was caused by a core system component reaching its maximum connection limit. Our engineering team successfully identified the issue, implemented a configuration update to increase connection capacity, and fully restored service by 10:40 UTC. \nWe are also conducting a full analysis to understand the unexpected usage increase and are enhancing our monitoring for earlier detection of similar events in the future. \nWe apologize for the inconvenience this may have caused.",
466
  "first_seen": "2026-09-04T07:06:16Z",
467
  "impact": "major",
468
- "last_seen": "2026-09-04T12:24:18Z",
469
  "resolved_at": "2025-11-11T10:50:20.250Z",
470
  "resolved_inferred": false,
471
  "started_at": "2025-11-11T09:36:03.178Z",
@@ -478,7 +480,7 @@
478
  "body": "On November 10th, a system optimization deployment led to a two-hour unavailability of core platform services due to a missing technical dependency. \n\nAlthough quickly resolved, the incident underscored the critical importance of strictly adhering to comprehensive quality assurance gates to ensure platform stability and prevent service disruption.",
479
  "first_seen": "2026-09-04T07:06:16Z",
480
  "impact": "major",
481
- "last_seen": "2026-09-04T12:24:18Z",
482
  "resolved_at": "2025-11-10T15:16:52.293Z",
483
  "resolved_inferred": false,
484
  "started_at": "2025-11-10T13:16:43.747Z",
@@ -491,7 +493,7 @@
491
  "body": "On October 20, some customers noticed duplicate timer execution logs appearing in the console. A fix was implemented to address this issue. \nOn November 3, another issue occurred in which parts of the timer log display were missing in the console. The investigation determined that the problem originated from a faulty service version introduced in a recent update. The affected version was identified and fixed. \nThe issue was fully resolved on November 7 at 13:07 UTC, and normal log visibility is now available for all customers. \n\nWe sincerely apologize for the inconvenience and appreciate your patience while we worked to restore full functionality.",
492
  "first_seen": "2026-09-04T07:06:16Z",
493
  "impact": "minor",
494
- "last_seen": "2026-09-04T12:24:18Z",
495
  "resolved_at": "2025-11-07T12:38:39.944Z",
496
  "resolved_inferred": false,
497
  "started_at": "2025-11-06T09:41:34.347Z",
@@ -504,7 +506,7 @@
504
  "body": "On October 30th, between 18:55 UTC and 21:22 UTC, customers experienced degraded success rates and timeouts when using the 1-Click Publish functionality. The issue, caused by an internal system component, was identified and resolved by our engineering team through a service restart, which immediately restored normal operation by 9:22 PM WET.",
505
  "first_seen": "2026-09-04T07:06:16Z",
506
  "impact": "minor",
507
- "last_seen": "2026-09-04T12:24:18Z",
508
  "resolved_at": "2025-10-30T21:24:39.984Z",
509
  "resolved_inferred": false,
510
  "started_at": "2025-10-30T20:46:05.199Z",
@@ -517,7 +519,7 @@
517
  "body": "On October 29th, at approximately 08:15 AM UTC, we observed a significant drop in service success rate primarily affecting Personal Edition instances. Users may have experienced timeout errors. \nAn immediate investigation traced the issue to a recent deployment. Reverting to the previous version resolved the problem, and all affected environments were restored to a healthy condition.",
518
  "first_seen": "2026-09-04T07:06:16Z",
519
  "impact": "major",
520
- "last_seen": "2026-09-04T12:24:18Z",
521
  "resolved_at": "2025-10-29T14:23:19.676Z",
522
  "resolved_inferred": false,
523
  "started_at": "2025-10-29T11:49:37.168Z",
@@ -530,7 +532,7 @@
530
  "body": "On October 20, some customers across all regions experienced issues logging in using external Identity Providers \\(IdPs\\), receiving an error or not being redirected to complete authentication. A temporary workaround was provided while the root cause, a faulty service version introduced in recent updates, was identified and reverted.\n\nThe issue was fully resolved on October 20 at 18:15 UTC, restoring normal login functionality for all customers. The incident duration was extended due to an unrelated AWS outage that impacted service rollback times.\n\nWe apologize for the inconvenience and appreciate your patience while we restored full functionality.",
531
  "first_seen": "2026-09-04T07:06:16Z",
532
  "impact": "major",
533
- "last_seen": "2026-09-04T12:24:18Z",
534
  "resolved_at": "2025-10-20T16:21:38.883Z",
535
  "resolved_inferred": false,
536
  "started_at": "2025-10-20T14:57:55.773Z",
@@ -543,7 +545,7 @@
543
  "body": "On October 20th, our cloud service provider experienced a high error rate and latency in the N. Virginia Region, which temporarily affected some of our internal tools and caused service disruption for\u00a0O11 and ODC customers. \nThe issue was first reported at 08:37 UTC\\+1 for ODC, affecting access to ODC Studio and running applications in ODC Portal. \nO11 had the first report at 08:54 UTC\\+1. Cloud customers weren't able to access their Service Centers, IdP Authentication started to present some failures, CloudWatch started to fail, and several other symptoms were felt, since it affected several networking resources, including 503 error messages. \nCustomers also experienced delays or interruptions using our services, including Forge, MABs, Licensing Registration, and accessing our Portals and telephony services. \nOur Support and Operations teams closely monitored the situation throughout the day, providing continuous updates to affected customers and coordinating internally to restore full functionality as quickly as possible. \nBy 14:06 UTC\\+1, it was reported that a full recovery of services had been achieved, and customers began confirming that their services were operating normally. However, later in the afternoon, around 16h32 UTC\\+1, we started again receiving reports of connectivity issues, affecting O11 customers. During the recovery process, due to latency errors, several customers experienced network connectivity issues. Our teams continued providing updates and ensured all systems remained stable. \nAWS confirmed that all its services returned to normal operations by 23:01 UTC\\+1. This disruption affected 142 AWS services, causing a direct impact on OutSystems services. They determined that the incident was caused by DNS resolution issues affecting DynamoDB. Following this, EC2 instance launches and Network Load Balancer health checks were also impacted, which in turn affected connectivity for Lambda, DynamoDB, and CloudWatch. \n\nWe apologize for any inconvenience caused and thank you for your patience.",
544
  "first_seen": "2026-09-04T07:06:16Z",
545
  "impact": "minor",
546
- "last_seen": "2026-09-04T12:24:18Z",
547
  "resolved_at": "2025-10-20T13:06:17.063Z",
548
  "resolved_inferred": false,
549
  "started_at": "2025-10-20T09:43:29.542Z",
@@ -556,7 +558,7 @@
556
  "body": "On October 15th, multiple customers reported being unable to log in to ODC Studio, temporarily interrupting their development work. Access through the ODC Portal remained available.\n\nThe issue was caused by recent Microsoft Windows updates affecting certain users. A temporary workaround was provided, and uninstalling the updates restored normal access. Microsoft has since released an update to resolve the problem, and customers should now be able to run Windows Update and install it.",
557
  "first_seen": "2026-09-04T07:06:16Z",
558
  "impact": "major",
559
- "last_seen": "2026-09-04T12:24:18Z",
560
  "resolved_at": "2025-10-15T23:26:27.616Z",
561
  "resolved_inferred": false,
562
  "started_at": "2025-10-15T17:25:25.422Z",
@@ -569,7 +571,7 @@
569
  "body": "On October 7th, 2025, the TimerManager service experienced an issue that prevented it from responding to requests, leading to customers being unable to execute their timers and continue development. The problem was resolved by restarting the affected service, which restored full functionality.",
570
  "first_seen": "2026-09-04T07:06:16Z",
571
  "impact": "major",
572
- "last_seen": "2026-09-04T12:24:18Z",
573
  "resolved_at": "2025-10-07T12:12:26.938Z",
574
  "resolved_inferred": false,
575
  "started_at": "2025-10-07T10:51:09.988Z",
@@ -582,7 +584,7 @@
582
  "body": "On Wednesday, August 20, between 18:09 UTC and 21:58 UTC, some customers experienced intermittent errors in the DEV environment in US East \\(Virginia\\) and Europe \\(Frankfurt\\). \nSupport teams identified a configuration issue that reduced service availability. A workaround was shared, and service was fully restored by 21:58 UTC. A permanent fix has since been applied to prevent similar issues in the future.",
583
  "first_seen": "2026-09-04T07:06:16Z",
584
  "impact": "minor",
585
- "last_seen": "2026-09-04T12:24:18Z",
586
  "resolved_at": "2025-08-20T21:43:07.992Z",
587
  "resolved_inferred": false,
588
  "started_at": "2025-08-20T19:39:01.654Z",
@@ -595,7 +597,7 @@
595
  "body": "On August 14th, a system update caused a critical service to restart with a faulty configuration, leading to connectivity issues for some applications. The issue was addressed and resolved on the same day by correcting the configuration.",
596
  "first_seen": "2026-09-04T07:06:16Z",
597
  "impact": "minor",
598
- "last_seen": "2026-09-04T12:24:18Z",
599
  "resolved_at": "2025-08-14T18:37:39.397Z",
600
  "resolved_inferred": false,
601
  "started_at": "2025-08-14T15:21:00.981Z",
 
3
  "slug": "outsystems",
4
  "platform": "statuspage",
5
  "status_url": "https://status.outsystems.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "partial",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
10
  "incidents": [
11
  {
12
+ "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T11:14:03Z",
14
  "impact": "major",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
+ "resolved_at": "2026-09-04T12:47:37.977Z",
17
+ "resolved_inferred": false,
18
  "started_at": "2026-09-04T11:15:06.692Z",
19
+ "state": "resolved",
20
  "title": "MABS Android and iOS builds timming out",
21
+ "updated_at": "2026-09-04T12:47:37.991Z",
22
  "url": "https://stspg.io/c5xghzgxc8ly"
23
  },
24
  {
25
  "body": "_Between August 28th and August 31st, 2026, users in the Asia Pacific \\(Sydney\\) region were unable to use Mentor in ODC Studio. Connection attempts returned an error stating, \"Mentor couldn't connect. Please go online and try again.\" Deployed applications and other ODC Studio functionality were not affected._ \n_As part of planned regional infrastructure work, Mentor connection requests from affected environments began being sent to a new regional destination. The services needed to handle those requests had not yet been deployed there, so every connection attempt failed. The change was applied ahead of those services becoming available._ \n_The issue was detected through customer reports. Automated monitoring did not alert on it, because connection requests were being sent to a destination where the supporting service was not yet running, so no failure signals were generated for our monitoring to detect._ \n_To restore service, we reversed the configuration change on a single environment and confirmed that Mentor connected successfully, then applied the same reversal across all affected environments. We verified recovery with each of the customers who had reported the issue._ \n_To prevent recurrence, the regional infrastructure work will not resume until all dependent services are available in the region. We are strengthening the validation applied before configuration updates of this kind, so that a change cannot be made ahead of the services it depends on. We are also reviewing our monitoring so that failures of this type are detected automatically rather than through customer reports._ \n_We apologise for any disruption caused and thank you for your patience._",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "critical",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-08-31T18:00:40.904Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-31T15:28:49.850Z",
 
38
  "body": "On August 26th, between 05:16 UTC and 16:26 UTC, some ODC users experienced delays in the execution of timers. Affected timers remained pending instead of running as scheduled, and subsequent runs did not start. Users in US East / Virginia and Asia Pacific / Singapore were affected. Applications themselves remained available throughout.\n\nThe issue was caused by a recent platform update that changed how a timer's status is recorded once it has run. Under that update, a timer whose status needed to be recorded more than once in sequence failed to update correctly, leaving it pending and blocking later scheduled executions. To restore service, our team returned the affected part of the platform to its previous version, which stopped the issue recurring for affected users. A permanent correction was then developed, validated and deployed across the platform, and we confirmed that timers were executing normally before closing the incident.\n\nWe are reviewing our monitoring of timer execution so that issues of this kind are detected automatically rather than through customer reports. We apologise for any disruption caused and thank you for your patience.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-08-26T16:33:04.484Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-08-26T05:16:49.409Z",
 
51
  "body": "On August 24th, 2026, some users experienced an issue affecting application deployments in ODC Portal. Affected users intermittently saw the error message: \"An error occurred while getting the generated code from revision. \\(OS-STGC-60005\\)\".\n\nThe issue was caused by an internal scaling tool that interfered with a backend service used to prepare deployment packages, causing delays and errors for some deployment requests. We fixed the scaling configuration to restore normal behavior.\n\nTo prevent a recurrence, we are working with the provider of the automated scaling tool to correct the underlying behavior, and have put a permanent safeguard in place to stop the affected service from being mismanaged by that tool going forward.\n\nWe apologize for any disruption caused and thank you for your patience.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-08-24T19:12:27.000Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-08-24T14:57:08.453Z",
 
64
  "body": "Between 20 August 9:52 UTC and 21 August 13:22 UTC, some users were unable to generate or edit applications using Mentor in the ODC Portal, and received the error OS-IDE-CONVERSATIONAL-50035. \nThe issue was caused by an outdated permission check that remained in place after a recent change to how the service communicates internally. \nWe removed the outdated check and confirmed that the Mentor App Generator App Editor recovered across the affected regions. \nWe apologise for the disruption this caused.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-08-21T16:20:15.691Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-08-21T10:54:59.659Z",
 
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-08-13T11:21:50.855Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-08-12T16:56:12.323Z",
 
90
  "body": "On August 12th, 2026, at approximately 02:56 UTC, we received our first customer report regarding an issue that affected the Application Configuration and IP Filter List features, resulting in these areas failing to load for a number of customers. Application publishing and runtime were not affected. Customers saw the error codes OS-APPC-60043 and OS-CFGC-GEN-60030. This prevented some users from completing required application configuration changes. Normal service was restored at 08:00 UTC.\n\nIt was caused by a recent update to an internal service that provides configuration data. The update unintentionally changed how requests were routed between instances of that service, so most requests for IP filter information reached an instance that could not answer them and timed out. Our team identified the faulty update and rolled it back across all environments to restore normal behavior.\n\nWe are improving our pre-release testing and monitoring so that this type of issue is caught before it reaches production, and adding monitoring coverage specifically for this failure mode.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-08-12T10:38:54.028Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-08-12T05:41:29.472Z",
 
103
  "body": "On August 10th, 2026, from 20:31 to 22:19 UTC, users in the South America / S\u00e3o Paulo region experienced errors when signing in to ODC. This prevented affected users from accessing their Production applications and also affected the ODC Portal and ODC Studio.\n\nThe issue was detected through customer reports and monitoring. Our investigation found that a fault in an internal caching component of our identity service was preventing it from issuing sign-in tokens, even though the service otherwise appeared to be running normally.\n\nTo restore service, our team restarted the affected identity service, which cleared the fault and allowed token issuance to resume. We confirmed with affected customers that sign-in and application access had returned to normal before closing the incident.\n\nWe have identified additional monitoring and preventive improvements for this component and are prioritising their rollout to help reduce the risk of similar issues recurring. We apologise for any disruption caused and thank you for your patience.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "major",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-08-11T07:54:40.255Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-08-10T20:48:01.967Z",
 
116
  "body": "On July 31st, 2026, an issue affected applications running in the Development Stage in Europe Central \\(Frankfurt\\). Applications experienced extended delays \\(2\u20133 minutes\\) and timeout errors when starting up from an idle state.\n\nThe issue lasted approximately a few hours and was detected through customer reports and platform monitoring. During this time, several customers in the region reported difficulties launching their applications in the Development Stage's Runtime.\n\nOur investigation identified a memory issue in a critical component responsible for automatically scaling applications based on incoming traffic. This component was consuming excessive memory and restarting repeatedly, which prevented applications from scaling up when first accessed. Our team immediately implemented an operational workaround by increasing resource limits for this component. This mitigation immediately allowed applications to scale up as expected.\n\nIn parallel, we developed a permanent code fix to address the root cause and deployed it on August 7th. The system remained stable, with no new occurrences during and after the deployment of the permanent fix.\n\nTo prevent similar issues, OutSystems is improving how we monitor and validate infrastructure configuration to catch memory and resource issues earlier, and we are enhancing our automated scaling components to handle traffic pattern changes more gracefully.\n\nWe apologise for any disruption caused and thank you for your patience.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-08-07T08:34:33.760Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-07-31T08:31:58.000Z",
 
129
  "body": "On July 30, 2026, between 15:19 and 15:59 UTC, customers in multiple regions experienced an outage affecting access to the OutSystems ODC Portal, preventing them from logging in or accessing their development environments. The incident was caused by the addition of a custom header, which prevented requests from reaching the portal. Following the code change rollback, service was restored by 15:59 UTC. To prevent similar incidents in the future, we are implementing additional automated testing to validate configuration changes before they are deployed to production and conducting a comprehensive review of our code review and testing procedures to catch such issues earlier in the development process. We appreciate your patience during this incident and apologize for any disruption to your work.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "none",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-07-30T18:39:10.991Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-07-30T18:39:10.882Z",
 
142
  "body": "On the 20th of July 2026, there was an issue with the wake-up functionality affecting Personal Editions. This occurred in all three regions \\(US East, Europe and Asia Pacific\\). \nUsers were unable to wake up their environments from hibernation. When attempting to wake up the environments, they either remained in hibernation or moved to a \"waking up\" state indefinitely, preventing access to applications. \nThis was caused by an issue in how our backend systems processed environment status updates. Due to messages being processed out of order, some environments' internal state was incorrectly reverted to 'hibernated' after they had already woken up successfully, even though the environment itself remained accessible on the backend. This caused the ODC Portal to keep showing an inaccurate 'hibernated' or 'waking up' status, and repeated wake-up attempts did not resolve it since the underlying state kept getting overwritten. \nWe identified the root cause on the 21st of July and deployed a code fix to correct the state synchronization. The fix started to be rolled out to all regions on 22nd of July and completed by the 23rd of July. All affected environments were woken up successfully. \nWe are implementing additional state verification checks to ensure the ODC Portal and backend systems remain in sync. A full technical review is underway to identify similar synchronization gaps across other features. \nWe apologize for any disruption caused and thank you for your patience.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "major",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2026-07-23T09:06:28.653Z",
147
  "resolved_inferred": false,
148
  "started_at": "2026-07-21T02:13:51.671Z",
 
155
  "body": "This incident has been resolved. ODC Personal Editions are now\noperating normally.\nIf you have not yet done so, please access your\nPersonal Edition by clicking \"Wake Up\" in the ODC Portal.\nIf you experience any issues, our support team is available to assist.\nThank you for your patience.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "major",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2026-07-20T17:37:51.191Z",
160
  "resolved_inferred": false,
161
  "started_at": "2026-07-20T11:46:15.940Z",
 
168
  "body": "On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2026-06-30T18:22:41.851Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-06-30T08:56:27.789Z",
 
181
  "body": "On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "major",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2026-06-29T18:07:13.000Z",
186
  "resolved_inferred": false,
187
  "started_at": "2026-06-29T04:28:44.715Z",
 
194
  "body": "On June 24th, an issue occurred that impacted ODC application deployments for non-administrator users across multiple regions, including Asia Pacific and Europe. Affected users experienced failures when attempting to deploy applications to higher stages and received an error during the build preparation step. Administrator accounts were not affected.\n\nThe issue was caused by a configuration change deployed on June 23rd, which introduced a technical mismatch in how permission roles were validated within the build pipeline, preventing non-admin users from initiating deployments. The engineering team identified the root cause and reversed the change.\n\nDeployments are now functioning normally for all affected users. We are conducting a post-incident review to prevent similar issues from occurring in the future.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2026-06-25T12:31:39.814Z",
199
  "resolved_inferred": false,
200
  "started_at": "2026-06-25T08:44:37.103Z",
 
207
  "body": "On June 22nd, an incident affected ODC users in the US East \\(N. Virginia\\) region. Users were unable to access any applications in the Development stage, receiving an \"Upstream Request Timeout\" error. Production and Test stages, as well as all other regions, were unaffected.\n\nThe incident was caused by a platform configuration change that prevented the component responsible for starting idle Development-stage applications on demand from functioning. As a result, when a request arrived, the application failed to start, causing the connection to time out at the gateway.\n\nThe issue was resolved by reverting the configuration change. The component fully recovered, app startup resumed, and normal service operation was verified.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "minor",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2026-06-22T12:42:49.313Z",
212
  "resolved_inferred": false,
213
  "started_at": "2026-06-22T11:37:51.203Z",
 
220
  "body": "On May 22, 2026, we deployed an update intended to improve internal diagnostics. This update added automatic comments to generated SQL statements. In a specific edge case, where count-based queries were used inside nested SQL statements, these added comments disrupted the structure of the query and caused it to fail. Affected applications returned runtime errors and certain database queries could not complete successfully. \nAfter deploying a fix for this, services were restored and all affected queries are now functioning normally. \nWe appreciate your patience while this was being resolved and remain committed to continuously improving the stability and reliability of the platform.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2026-05-25T13:37:01.699Z",
225
  "resolved_inferred": false,
226
  "started_at": "2026-05-22T14:58:38.280Z",
 
233
  "body": "On May 8, 2026, at 12:03 AM UTC, ODC and O11 Personal Environments in the N. Virginia region experienced a service disruption caused by an AWS infrastructure event affecting a single Availability Zone. The disruption was related to an external power and cooling issue that impacted the availability of underlying AWS services. \nCustomers experienced service unavailability, including issues with logging in and publishing applications.The impact was limited to O11 Personal Environments and a small subset of users, while impact on ODC remained contained. \nAs AWS services recovered, many OutSystems environments resumed normal operation automatically. Some environments required additional recovery actions to fully restore service availability. \nFor ODC, the incident was fully resolved on May 9, 2026, at 3:30 AM UTC. Recovery efforts for O11 Personal Environments continued afterward due to the additional complexity of restoring affected environments. \nAll services are now operating as expected, and no user action is required.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2026-05-11T16:12:05.338Z",
238
  "resolved_inferred": false,
239
  "started_at": "2026-05-08T11:56:03.115Z",
 
246
  "body": "This incident has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2026-04-21T10:19:47.188Z",
251
  "resolved_inferred": false,
252
  "started_at": "2026-04-21T02:36:07.374Z",
 
259
  "body": "On April 13,2026 between 1:13 and 3:07 AM UTC, an incident occurred that prevented users from logging in to the ODC Portal across multiple regions. The issue was caused by a deployment of a Identity Service that required a database schema change that had not yet been applied, resulting in authentication failures.\n\nService was restored after the team initiated a rollback to the previous stable version. Validation confirmed that login functionality was restored for all users. \n\nThe incident is fully resolved, and all services are operating as expected.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "critical",
262
+ "last_seen": "2026-09-04T14:19:03Z",
263
  "resolved_at": "2026-04-13T03:30:32.085Z",
264
  "resolved_inferred": false,
265
  "started_at": "2026-04-13T02:24:21.692Z",
 
272
  "body": "The issues affecting our services have been resolved, and all systems are now operating normally. We apologize for any disruption this may have caused to your workflows.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "critical",
275
+ "last_seen": "2026-09-04T14:19:03Z",
276
  "resolved_at": "2026-03-30T11:22:22.790Z",
277
  "resolved_inferred": false,
278
  "started_at": "2026-03-29T01:06:32.583Z",
 
285
  "body": "On March 19th, 2026, at approximately 06:43 UTC, an issue was identified affecting ODC, where some users were unable to complete the login process for the ODC Portal and ODC Studio when using external Identity Providers. Affected users encountered an error message stating \"Email verification not supported\" or were blocked from accessing their accounts because the system could not verify their email addresses via the external provider's claims.\n\nThe incident was caused by a configuration change intended to strictly enforce email verification from external providers. This change inadvertently bypassed a native fallback verification process that certain users relied upon when their external providers did not share specific verification data.\n\nThe issue was resolved by 11:00 UTC on March 19th following a rollback to the previous service versions. To prevent recurrence, future updates to this functionality will be implemented via a gradual rollout plan, including additional validation steps to ensure all identity provider configurations are fully supported.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "major",
288
+ "last_seen": "2026-09-04T14:19:03Z",
289
  "resolved_at": "2026-03-19T11:32:05.121Z",
290
  "resolved_inferred": false,
291
  "started_at": "2026-03-19T09:35:30.445Z",
 
298
  "body": "On March 4th, 2026, between 2:39 am and 10:29 am UTC, ODC experienced an incident that prevented users from accessing the App Detail screen and performing app configurations across all stages. The runtime of existing applications was not affected by this issue. \nThe root cause was a subscription validation misalignment between internal APIs and ODC Portal, which resulted in errors for customers without the ODC Sentry add-on. \nTo prevent future occurrences, we are updating ODC Portal to verify subscription status in alignment with these APIs and improving UI error handling to ensure failures like this do not obstruct the overall page experience.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "major",
301
+ "last_seen": "2026-09-04T14:19:03Z",
302
  "resolved_at": "2026-03-04T10:41:33.282Z",
303
  "resolved_inferred": false,
304
  "started_at": "2026-03-04T09:09:44.870Z",
 
311
  "body": "All customers impacted by this incident have been contacted and supported individually. While the Middle East region continues to be affected by the ongoing geopolitical situation and AWS continues to report the region as impacted, OutSystems has completed its direct response to every affected organization. \nThe affected services remain flagged as a major outage while these conditions persist. Customers who need further assistance can contact OutSystems Support by raising a new ticket or continuing their existing case through Support Services.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "critical",
314
+ "last_seen": "2026-09-04T14:19:03Z",
315
  "resolved_at": "2026-07-03T14:41:51.440Z",
316
  "resolved_inferred": false,
317
  "started_at": "2026-03-01T16:33:04.355Z",
 
324
  "body": "On January 30th, several ODC customers experienced intermittent issues where the username attribute was missing data from the User entity within applications. \nThe cause was identified as a bug in a recent release of an identity component. This issue prevented specific user and identity provider data from correctly populating the Username Attribute. \nThe incident was resolved by rolling back the affected release. A corrected version has since been deployed to ensure consistent data availability and prevent future occurrences.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "major",
327
+ "last_seen": "2026-09-04T14:19:03Z",
328
  "resolved_at": "2026-01-30T12:43:09.769Z",
329
  "resolved_inferred": false,
330
  "started_at": "2026-01-29T20:00:44.115Z",
 
337
  "body": "On January 27th, we experienced a service disruption in Mentor affecting APAC and EMEA regions. Users encountered elevated error rates and a loss of functionality for Mentor features.\n\nThe incident was triggered by a third-party service outage, which hosts the models supporting our Data & AI services. While a fallback system was in place, it also became unavailable during the outage. Furthermore, the impact of the external service disruption also prevented our team from implementing a manual configuration fix immediately.\n\nWe are also working toward an automated fallback mechanism to minimize the need for manual intervention. Additionally, we are implementing agent-level fallbacks to different models at the product level.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "major",
340
+ "last_seen": "2026-09-04T14:19:03Z",
341
  "resolved_at": "2026-01-27T18:20:48.471Z",
342
  "resolved_inferred": false,
343
  "started_at": "2026-01-27T12:53:02.416Z",
 
350
  "body": "On January 22nd, between 15:00 UTC and 17:00 UTC, an incident affected ODC in the Europe \\(Frankfurt\\) region. Users experienced issues with One-Click Publish, specifically resulting in build timeouts and publish failures. \n\nThe issue was caused by a communication failure between the internal queuing system and the Build Service, which prevented build processes from completing. \n\nOur team resolved the incident by restarting the Build Service and restoring communication. Normal service has been restored, and we are evaluating measures to improve system resilience moving forward.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "major",
353
+ "last_seen": "2026-09-04T14:19:03Z",
354
  "resolved_at": "2026-01-22T16:52:18.961Z",
355
  "resolved_inferred": false,
356
  "started_at": "2026-01-22T15:29:09.888Z",
 
363
  "body": "On January 16th, a service change related to an ongoing migration caused a temporary issue where customers were unable to log in using their custom domains. Our engineering team immediately identified the cause and implemented a mitigation to resolve the issue quickly by temporarily disabling the custom domain redirection feature. A controlled restart of system deployments was performed to expedite this fix.\n\nTo ensure stability and prevent recurrence, a technical recommendation has been made to enhance the system. This improvement will increase resilience to future updates and configuration changes, helping maintain continuous operation without service interruptions.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "major",
366
+ "last_seen": "2026-09-04T14:19:03Z",
367
  "resolved_at": "2026-01-16T14:35:08.339Z",
368
  "resolved_inferred": false,
369
  "started_at": "2026-01-16T10:13:39.978Z",
 
376
  "body": "On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.\n\nThe incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation.\n\nTo resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.\n\nTo prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "major",
379
+ "last_seen": "2026-09-04T14:19:03Z",
380
  "resolved_at": "2025-12-08T15:46:04.126Z",
381
  "resolved_inferred": false,
382
  "started_at": "2025-12-08T13:36:21.621Z",
 
389
  "body": "On December 8th, we experienced an issue that affected application publishing. This resulted in users being unable to publish any applications in the Development stage across all regions, encountering the error code OS-DPL-40802 \\(Deployment timeout\\).\n\nThe root cause of the incident was a new version of an internal service that was deployed around the same time the problem started. This new version contained changes that caused application deployments to fail.\n\nThe issue was resolved by reverting the internal service to the previous stable version.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "major",
392
+ "last_seen": "2026-09-04T14:19:03Z",
393
  "resolved_at": "2025-12-08T11:12:45.118Z",
394
  "resolved_inferred": false,
395
  "started_at": "2025-12-08T10:15:04.809Z",
 
402
  "body": "On November 26th, an issue was experienced affecting Personal Editions users, resulting in users seeing a \u201cno permissions\u201d page and being unable to use their Personal Edition environments. Normal service was restored at 21:00 UTC.\n\nThe incident was caused by the reconfiguration step used to fix an earlier issue. This step correctly re-applied the Identity Provider \\(IdP\\) but also unintentionally made the affected Personal Editions environments available for re-assignment. As a result, many of the previously fixed Personal Editions were re-assigned to \"second\" users who were created without any permissions upon first login, leading to the \u201cno permissions\u201d screen.\n\nTo prevent new occurrences, all Personal Editions environments created during the faulty period that had gone through the reconfiguration were discarded. Impacted users were proactively informed and instructed to request a new Personal Edition.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "major",
405
+ "last_seen": "2026-09-04T14:19:03Z",
406
  "resolved_at": "2025-11-26T21:01:14.873Z",
407
  "resolved_inferred": false,
408
  "started_at": "2025-11-26T10:07:52.000Z",
 
415
  "body": "On November 25th, around 11:15 UTC, we experienced an issue affecting Personal Editions, resulting in users being unable to log in and consistently seeing the error \u201cIncorrect username or password \\(OS-UAUC-60004\\)\u201d despite using valid credentials in the regions of US East \\(Ohio\\), Europe \\(Ireland\\), and Asia Pacific \\(Singapore\\). Normal service was restored by approximately 17:00 UTC the same day.\n\nThe incident was caused by an issue in provisioning that led Personal Editions to not have the built-in community provider configured as an Identity Provider. This resulted in the login failures when users attempted to access their Personal Editions.\n\nTo prevent new occurrences, the provisioning logic was updated to treat a similar empty response as an error, triggering an internal alert and preventing affected environments from being handed out as ready-to-use. Additionally, a targeted reconfiguration job was run to correctly apply the required identity provider to all impacted Personal Editions, which restored normal login functionality",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "major",
418
+ "last_seen": "2026-09-04T14:19:03Z",
419
  "resolved_at": "2025-11-25T17:06:54.578Z",
420
  "resolved_inferred": false,
421
  "started_at": "2025-11-25T12:37:30.726Z",
 
428
  "body": "On November 24, 2025, a new version of our deployment service was released, including an internal library update intended to optimize the processing of external libraries. This update inadvertently caused a logic error that made deployments hang during certain operations, leading to intermittent timeouts for customers deploying external libraries or applications that depend on them. Not all deployments were affected, and the impact varied by region and library volume. We immediately reverted the service to the previous stable version, restoring normal deployment operations. \n\nWe are working to correct the issue in the internal library and will reintroduce the optimization after thorough validation to prevent future disruptions. \n\nWe apologize for the inconvenience and appreciate your patience.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "major",
431
+ "last_seen": "2026-09-04T14:19:03Z",
432
  "resolved_at": "2025-11-24T12:09:07.383Z",
433
  "resolved_inferred": false,
434
  "started_at": "2025-11-24T11:46:09.029Z",
 
441
  "body": "On November 18th, we experienced an issue that prevented users with Personal Editions from accessing the ODC Portal login page. Customers who were affected saw the error message: \"Something unexpected happened during login. Please try logging in again using a new tab or a different browser\". Normal service was restored at 11:09 AM UTC.\n\nThe incident was caused by a recent system update that introduced an error in how login data was processed. Full access was restored after we reverted the affected system component to its previous version. We apologize for the inconvenience this caused.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "critical",
444
+ "last_seen": "2026-09-04T14:19:03Z",
445
  "resolved_at": "2025-11-18T11:28:20.067Z",
446
  "resolved_inferred": false,
447
  "started_at": "2025-11-18T09:56:52.556Z",
 
454
  "body": "A platform-wide issue was identified where log messages generated within successful Timers were inconsistently or completely missing from the monitoring interface. \nThe root cause was a technical race condition during a critical component startup, which prevented logs from reaching the central logging system. Engineering team developed and deployed an update that resolved the issue, and extensive monitoring has confirmed the platform is now stable, with all Timer-originated log entries appearing correctly.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "minor",
457
+ "last_seen": "2026-09-04T14:19:03Z",
458
  "resolved_at": "2025-11-17T17:45:47.025Z",
459
  "resolved_inferred": false,
460
  "started_at": "2025-11-14T14:26:56.766Z",
 
467
  "body": "Customers experienced intermittent service issues with core operations, including deployments and authentication, between 2:58 and 10:40 UTC. \nThe disruption was caused by a core system component reaching its maximum connection limit. Our engineering team successfully identified the issue, implemented a configuration update to increase connection capacity, and fully restored service by 10:40 UTC. \nWe are also conducting a full analysis to understand the unexpected usage increase and are enhancing our monitoring for earlier detection of similar events in the future. \nWe apologize for the inconvenience this may have caused.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "major",
470
+ "last_seen": "2026-09-04T14:19:03Z",
471
  "resolved_at": "2025-11-11T10:50:20.250Z",
472
  "resolved_inferred": false,
473
  "started_at": "2025-11-11T09:36:03.178Z",
 
480
  "body": "On November 10th, a system optimization deployment led to a two-hour unavailability of core platform services due to a missing technical dependency. \n\nAlthough quickly resolved, the incident underscored the critical importance of strictly adhering to comprehensive quality assurance gates to ensure platform stability and prevent service disruption.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "major",
483
+ "last_seen": "2026-09-04T14:19:03Z",
484
  "resolved_at": "2025-11-10T15:16:52.293Z",
485
  "resolved_inferred": false,
486
  "started_at": "2025-11-10T13:16:43.747Z",
 
493
  "body": "On October 20, some customers noticed duplicate timer execution logs appearing in the console. A fix was implemented to address this issue. \nOn November 3, another issue occurred in which parts of the timer log display were missing in the console. The investigation determined that the problem originated from a faulty service version introduced in a recent update. The affected version was identified and fixed. \nThe issue was fully resolved on November 7 at 13:07 UTC, and normal log visibility is now available for all customers. \n\nWe sincerely apologize for the inconvenience and appreciate your patience while we worked to restore full functionality.",
494
  "first_seen": "2026-09-04T07:06:16Z",
495
  "impact": "minor",
496
+ "last_seen": "2026-09-04T14:19:03Z",
497
  "resolved_at": "2025-11-07T12:38:39.944Z",
498
  "resolved_inferred": false,
499
  "started_at": "2025-11-06T09:41:34.347Z",
 
506
  "body": "On October 30th, between 18:55 UTC and 21:22 UTC, customers experienced degraded success rates and timeouts when using the 1-Click Publish functionality. The issue, caused by an internal system component, was identified and resolved by our engineering team through a service restart, which immediately restored normal operation by 9:22 PM WET.",
507
  "first_seen": "2026-09-04T07:06:16Z",
508
  "impact": "minor",
509
+ "last_seen": "2026-09-04T14:19:03Z",
510
  "resolved_at": "2025-10-30T21:24:39.984Z",
511
  "resolved_inferred": false,
512
  "started_at": "2025-10-30T20:46:05.199Z",
 
519
  "body": "On October 29th, at approximately 08:15 AM UTC, we observed a significant drop in service success rate primarily affecting Personal Edition instances. Users may have experienced timeout errors. \nAn immediate investigation traced the issue to a recent deployment. Reverting to the previous version resolved the problem, and all affected environments were restored to a healthy condition.",
520
  "first_seen": "2026-09-04T07:06:16Z",
521
  "impact": "major",
522
+ "last_seen": "2026-09-04T14:19:03Z",
523
  "resolved_at": "2025-10-29T14:23:19.676Z",
524
  "resolved_inferred": false,
525
  "started_at": "2025-10-29T11:49:37.168Z",
 
532
  "body": "On October 20, some customers across all regions experienced issues logging in using external Identity Providers \\(IdPs\\), receiving an error or not being redirected to complete authentication. A temporary workaround was provided while the root cause, a faulty service version introduced in recent updates, was identified and reverted.\n\nThe issue was fully resolved on October 20 at 18:15 UTC, restoring normal login functionality for all customers. The incident duration was extended due to an unrelated AWS outage that impacted service rollback times.\n\nWe apologize for the inconvenience and appreciate your patience while we restored full functionality.",
533
  "first_seen": "2026-09-04T07:06:16Z",
534
  "impact": "major",
535
+ "last_seen": "2026-09-04T14:19:03Z",
536
  "resolved_at": "2025-10-20T16:21:38.883Z",
537
  "resolved_inferred": false,
538
  "started_at": "2025-10-20T14:57:55.773Z",
 
545
  "body": "On October 20th, our cloud service provider experienced a high error rate and latency in the N. Virginia Region, which temporarily affected some of our internal tools and caused service disruption for\u00a0O11 and ODC customers. \nThe issue was first reported at 08:37 UTC\\+1 for ODC, affecting access to ODC Studio and running applications in ODC Portal. \nO11 had the first report at 08:54 UTC\\+1. Cloud customers weren't able to access their Service Centers, IdP Authentication started to present some failures, CloudWatch started to fail, and several other symptoms were felt, since it affected several networking resources, including 503 error messages. \nCustomers also experienced delays or interruptions using our services, including Forge, MABs, Licensing Registration, and accessing our Portals and telephony services. \nOur Support and Operations teams closely monitored the situation throughout the day, providing continuous updates to affected customers and coordinating internally to restore full functionality as quickly as possible. \nBy 14:06 UTC\\+1, it was reported that a full recovery of services had been achieved, and customers began confirming that their services were operating normally. However, later in the afternoon, around 16h32 UTC\\+1, we started again receiving reports of connectivity issues, affecting O11 customers. During the recovery process, due to latency errors, several customers experienced network connectivity issues. Our teams continued providing updates and ensured all systems remained stable. \nAWS confirmed that all its services returned to normal operations by 23:01 UTC\\+1. This disruption affected 142 AWS services, causing a direct impact on OutSystems services. They determined that the incident was caused by DNS resolution issues affecting DynamoDB. Following this, EC2 instance launches and Network Load Balancer health checks were also impacted, which in turn affected connectivity for Lambda, DynamoDB, and CloudWatch. \n\nWe apologize for any inconvenience caused and thank you for your patience.",
546
  "first_seen": "2026-09-04T07:06:16Z",
547
  "impact": "minor",
548
+ "last_seen": "2026-09-04T14:19:03Z",
549
  "resolved_at": "2025-10-20T13:06:17.063Z",
550
  "resolved_inferred": false,
551
  "started_at": "2025-10-20T09:43:29.542Z",
 
558
  "body": "On October 15th, multiple customers reported being unable to log in to ODC Studio, temporarily interrupting their development work. Access through the ODC Portal remained available.\n\nThe issue was caused by recent Microsoft Windows updates affecting certain users. A temporary workaround was provided, and uninstalling the updates restored normal access. Microsoft has since released an update to resolve the problem, and customers should now be able to run Windows Update and install it.",
559
  "first_seen": "2026-09-04T07:06:16Z",
560
  "impact": "major",
561
+ "last_seen": "2026-09-04T14:19:03Z",
562
  "resolved_at": "2025-10-15T23:26:27.616Z",
563
  "resolved_inferred": false,
564
  "started_at": "2025-10-15T17:25:25.422Z",
 
571
  "body": "On October 7th, 2025, the TimerManager service experienced an issue that prevented it from responding to requests, leading to customers being unable to execute their timers and continue development. The problem was resolved by restarting the affected service, which restored full functionality.",
572
  "first_seen": "2026-09-04T07:06:16Z",
573
  "impact": "major",
574
+ "last_seen": "2026-09-04T14:19:03Z",
575
  "resolved_at": "2025-10-07T12:12:26.938Z",
576
  "resolved_inferred": false,
577
  "started_at": "2025-10-07T10:51:09.988Z",
 
584
  "body": "On Wednesday, August 20, between 18:09 UTC and 21:58 UTC, some customers experienced intermittent errors in the DEV environment in US East \\(Virginia\\) and Europe \\(Frankfurt\\). \nSupport teams identified a configuration issue that reduced service availability. A workaround was shared, and service was fully restored by 21:58 UTC. A permanent fix has since been applied to prevent similar issues in the future.",
585
  "first_seen": "2026-09-04T07:06:16Z",
586
  "impact": "minor",
587
+ "last_seen": "2026-09-04T14:19:03Z",
588
  "resolved_at": "2025-08-20T21:43:07.992Z",
589
  "resolved_inferred": false,
590
  "started_at": "2025-08-20T19:39:01.654Z",
 
597
  "body": "On August 14th, a system update caused a critical service to restart with a faulty configuration, leading to connectivity issues for some applications. The issue was addressed and resolved on the same day by correcting the configuration.",
598
  "first_seen": "2026-09-04T07:06:16Z",
599
  "impact": "minor",
600
+ "last_seen": "2026-09-04T14:19:03Z",
601
  "resolved_at": "2025-08-14T18:37:39.397Z",
602
  "resolved_inferred": false,
603
  "started_at": "2025-08-14T15:21:00.981Z",
api/v/ovhcloud.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "ovhcloud",
4
  "platform": "status.io",
5
  "status_url": "https://status.us.ovhcloud.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "maintenance",
8
  "history_backfilled": false,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -11,7 +11,7 @@
11
  {
12
  "body": "We're currently investigating an issue where Delivery operations are stuck in \"Doing\". As a result, orders placed may be significantly delayed while we work on this resolution.\r\n\r\nOur teams are actively working toward a resolution, and updates will be shared as progress is made. We apologize for the inconvenience.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
- "last_seen": "2026-09-04T12:24:18Z",
15
  "started_at": "2026-09-03T18:36:08.957Z",
16
  "state": "investigating",
17
  "title": "Delays in Server Delivery due to Backend Processing Issue",
@@ -21,7 +21,7 @@
21
  {
22
  "body": "Cancellation reversal is currently not working as intended. If the VPS is set to cancel and a request is made to cancel the service cancellation, it remains flagged for removal. \r\n\r\nIf you are attempting to remove services for VPS, please reach out to our support team by opening a ticket. \r\n\r\n",
23
  "first_seen": "2026-09-04T07:06:16Z",
24
- "last_seen": "2026-09-04T12:24:18Z",
25
  "started_at": "2026-08-25T14:42:14.789Z",
26
  "state": "investigating",
27
  "title": "Service Cancelation issue for VPS Product",
@@ -31,7 +31,7 @@
31
  {
32
  "first_seen": "2026-09-04T07:06:16Z",
33
  "impact": "maintenance",
34
- "last_seen": "2026-09-04T12:24:18Z",
35
  "started_at": "2026-08-20T04:05:04.640Z",
36
  "state": "maintenance",
37
  "title": "Maintenance to perform vCSA Minor Upgrade to 8.0U3k",
@@ -40,7 +40,7 @@
40
  {
41
  "body": "OVHcloud support staff is currently monitoring a rack fault in 120A02B. Power to the rack was temporarily disrupted and has been restored . All servers on the rack are currently backup. If you are experiencing any issues please reach out to OVHcloud support staff.",
42
  "first_seen": "2026-09-04T07:06:16Z",
43
- "last_seen": "2026-09-04T12:24:18Z",
44
  "started_at": "2026-04-03T14:02:00.000Z",
45
  "state": "investigating",
46
  "title": "[VIN1] Server Power Loss VIN0120A02B",
@@ -50,7 +50,7 @@
50
  {
51
  "body": "The down VPS host has been brought back up, and all instances are running normally.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
- "last_seen": "2026-09-04T12:24:18Z",
54
  "started_at": "2026-03-24T19:52:00.000Z",
55
  "state": "investigating",
56
  "title": "One VPS host down in VIN",
 
3
  "slug": "ovhcloud",
4
  "platform": "status.io",
5
  "status_url": "https://status.us.ovhcloud.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "maintenance",
8
  "history_backfilled": false,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
11
  {
12
  "body": "We're currently investigating an issue where Delivery operations are stuck in \"Doing\". As a result, orders placed may be significantly delayed while we work on this resolution.\r\n\r\nOur teams are actively working toward a resolution, and updates will be shared as progress is made. We apologize for the inconvenience.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
+ "last_seen": "2026-09-04T14:19:03Z",
15
  "started_at": "2026-09-03T18:36:08.957Z",
16
  "state": "investigating",
17
  "title": "Delays in Server Delivery due to Backend Processing Issue",
 
21
  {
22
  "body": "Cancellation reversal is currently not working as intended. If the VPS is set to cancel and a request is made to cancel the service cancellation, it remains flagged for removal. \r\n\r\nIf you are attempting to remove services for VPS, please reach out to our support team by opening a ticket. \r\n\r\n",
23
  "first_seen": "2026-09-04T07:06:16Z",
24
+ "last_seen": "2026-09-04T14:19:03Z",
25
  "started_at": "2026-08-25T14:42:14.789Z",
26
  "state": "investigating",
27
  "title": "Service Cancelation issue for VPS Product",
 
31
  {
32
  "first_seen": "2026-09-04T07:06:16Z",
33
  "impact": "maintenance",
34
+ "last_seen": "2026-09-04T14:19:03Z",
35
  "started_at": "2026-08-20T04:05:04.640Z",
36
  "state": "maintenance",
37
  "title": "Maintenance to perform vCSA Minor Upgrade to 8.0U3k",
 
40
  {
41
  "body": "OVHcloud support staff is currently monitoring a rack fault in 120A02B. Power to the rack was temporarily disrupted and has been restored . All servers on the rack are currently backup. If you are experiencing any issues please reach out to OVHcloud support staff.",
42
  "first_seen": "2026-09-04T07:06:16Z",
43
+ "last_seen": "2026-09-04T14:19:03Z",
44
  "started_at": "2026-04-03T14:02:00.000Z",
45
  "state": "investigating",
46
  "title": "[VIN1] Server Power Loss VIN0120A02B",
 
50
  {
51
  "body": "The down VPS host has been brought back up, and all instances are running normally.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
+ "last_seen": "2026-09-04T14:19:03Z",
54
  "started_at": "2026-03-24T19:52:00.000Z",
55
  "state": "investigating",
56
  "title": "One VPS host down in VIN",
api/v/packagecloud.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "packagecloud",
4
  "platform": "statuspage",
5
  "status_url": "http://www.packagecloudstatus.io",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "# Summary\n\nAt 09:52AM UTC, we received the first customer report indicating HTTP 500 errors during Debian package uploads. Additional reports followed throughout the day, confirming that multiple package types and customers were affected. After an internal investigation, the issue was declared an incident at 18:19PM UTC.\n\nThe underlying cause was found to be insufficient disk space on a subset of ECS tasks responsible for handling file uploads. These tasks had reached their disk capacity, preventing them from completing upload operations. Because the tasks were running at maximum disk usage, they also could not be automatically cycled out by ECS, allowing the problem to persist.\n\nDuring the investigation we observed an increase in device maximum capacity errors, and inspection of the ECS cluster revealed tasks of varying ages. This correlated with the accumulation of temporary files generated during package extraction and processing. Although temporary file cleanup mechanisms exist, they did not adequately prevent disk saturation.\n\nAs a short-term remediation, a deploy was triggered to refresh all ECS tasks, which replaced the existing tasks with new ones. Following this deployment, upload functionality stabilized and no further customer impacting errors were observed. The issue was considered mitigated at 20:19PM UTC.\n\nSubsequent analysis confirmed that temporary file usage was a significant contributor to disk exhaustion. Additional improvements were implemented to ensure temporary files are consistently closed and cleaned up, regardless of whether errors occur during processing.\n\n## Changes we\u2019re making:\n\n \nTo reduce the likelihood of similar incidents in the future, we are implementing the following long-term improvements:\n\n* Strengthening disk usage observability: Enhanced monitoring now provides realtime insight into ECS task disk consumption, enabling earlier detection of abnormal usage.\n* Improving temporary file lifecycle management: Further audit and cleanup of temporary file handling across the codebase is underway to minimize unnecessary disk usage.\n* Refining ECS task lifecycle practices: We are reviewing our deployment and recycling strategy to ensure tasks do not remain active long enough to accumulate excessive temporary data.\n* Enhancing health checks: We are evaluating load balancer health check behavior to ensure that resource-degraded tasks \\(including those with insufficient disk\\) are identified and replaced more promptly.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2025-11-26T05:00:00.000-08:00",
17
  "resolved_inferred": false,
18
  "started_at": "2025-11-26T05:00:00.000-08:00",
@@ -25,7 +25,7 @@
25
  "body": "## Service Impact\n\nOn October 24th, 2025 from approximately 01:53AM UTC until 04:24AM UTC our package download service experienced an outage affecting customer access. This was confirmed to have impacted Debian and RubyGems.\n\n## Incident Summary\n\nAt 01:13AM UTC we updated the S3 Bucket Policy for an S3 bucket containing customer packages via Terraform as part of a larger re-architecting project.\n\nWe received customer reports about Debian package download issues from 01:53AM UTC and started doing isolated, per-customer investigations. At 03:40AM UTC we concluded that the issues were not isolated and declared the incident. More members from our team were called to help investigate the problem, where we found that service for pulling RubyGems had also been impacted. Around 04:00 UTC, the new bucket policy deployed at 01:13AM UTC was identified as a main factor to the access failure and was removed.\n\nAt 04:19AM UTC our team identified that updating the IAM policy via Terraform did not have the expected result of merging with the pre-existing policy, but rather inadvertently overwrote the pre-existing access policies, causing the loss of access permissions necessary for package downloads. Afterwards it became apparent to our team making these changes that this particular behavior is a [known issue](https://github.com/hashicorp/terraform-provider-aws/issues/6334) with the Terraform AWS provider, which contributed to the difficulty of detection and prevention, thereby increasing the likelihood of the incident occurring for those unaware.\n\nAfter redeploying the pre-existing S3 bucket IAM policy, we confirmed service functionality for Debian package downloads was restored at 04:24 AM UTC. The team subsequently verified that pulling RubyGems and other supported package types were also functioning as expected, and the incident was closed at 04:47 AM UTC.\n\n## Changes we're making\n\nWe are revising our monitoring approaches to identify and address service disruptions proactively, while also improving our communication processes to ensure timely and accurate customer updates.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2025-10-23T21:40:49.301-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2025-10-23T21:12:13.320-07:00",
 
3
  "slug": "packagecloud",
4
  "platform": "statuspage",
5
  "status_url": "http://www.packagecloudstatus.io",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "# Summary\n\nAt 09:52AM UTC, we received the first customer report indicating HTTP 500 errors during Debian package uploads. Additional reports followed throughout the day, confirming that multiple package types and customers were affected. After an internal investigation, the issue was declared an incident at 18:19PM UTC.\n\nThe underlying cause was found to be insufficient disk space on a subset of ECS tasks responsible for handling file uploads. These tasks had reached their disk capacity, preventing them from completing upload operations. Because the tasks were running at maximum disk usage, they also could not be automatically cycled out by ECS, allowing the problem to persist.\n\nDuring the investigation we observed an increase in device maximum capacity errors, and inspection of the ECS cluster revealed tasks of varying ages. This correlated with the accumulation of temporary files generated during package extraction and processing. Although temporary file cleanup mechanisms exist, they did not adequately prevent disk saturation.\n\nAs a short-term remediation, a deploy was triggered to refresh all ECS tasks, which replaced the existing tasks with new ones. Following this deployment, upload functionality stabilized and no further customer impacting errors were observed. The issue was considered mitigated at 20:19PM UTC.\n\nSubsequent analysis confirmed that temporary file usage was a significant contributor to disk exhaustion. Additional improvements were implemented to ensure temporary files are consistently closed and cleaned up, regardless of whether errors occur during processing.\n\n## Changes we\u2019re making:\n\n \nTo reduce the likelihood of similar incidents in the future, we are implementing the following long-term improvements:\n\n* Strengthening disk usage observability: Enhanced monitoring now provides realtime insight into ECS task disk consumption, enabling earlier detection of abnormal usage.\n* Improving temporary file lifecycle management: Further audit and cleanup of temporary file handling across the codebase is underway to minimize unnecessary disk usage.\n* Refining ECS task lifecycle practices: We are reviewing our deployment and recycling strategy to ensure tasks do not remain active long enough to accumulate excessive temporary data.\n* Enhancing health checks: We are evaluating load balancer health check behavior to ensure that resource-degraded tasks \\(including those with insufficient disk\\) are identified and replaced more promptly.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2025-11-26T05:00:00.000-08:00",
17
  "resolved_inferred": false,
18
  "started_at": "2025-11-26T05:00:00.000-08:00",
 
25
  "body": "## Service Impact\n\nOn October 24th, 2025 from approximately 01:53AM UTC until 04:24AM UTC our package download service experienced an outage affecting customer access. This was confirmed to have impacted Debian and RubyGems.\n\n## Incident Summary\n\nAt 01:13AM UTC we updated the S3 Bucket Policy for an S3 bucket containing customer packages via Terraform as part of a larger re-architecting project.\n\nWe received customer reports about Debian package download issues from 01:53AM UTC and started doing isolated, per-customer investigations. At 03:40AM UTC we concluded that the issues were not isolated and declared the incident. More members from our team were called to help investigate the problem, where we found that service for pulling RubyGems had also been impacted. Around 04:00 UTC, the new bucket policy deployed at 01:13AM UTC was identified as a main factor to the access failure and was removed.\n\nAt 04:19AM UTC our team identified that updating the IAM policy via Terraform did not have the expected result of merging with the pre-existing policy, but rather inadvertently overwrote the pre-existing access policies, causing the loss of access permissions necessary for package downloads. Afterwards it became apparent to our team making these changes that this particular behavior is a [known issue](https://github.com/hashicorp/terraform-provider-aws/issues/6334) with the Terraform AWS provider, which contributed to the difficulty of detection and prevention, thereby increasing the likelihood of the incident occurring for those unaware.\n\nAfter redeploying the pre-existing S3 bucket IAM policy, we confirmed service functionality for Debian package downloads was restored at 04:24 AM UTC. The team subsequently verified that pulling RubyGems and other supported package types were also functioning as expected, and the incident was closed at 04:47 AM UTC.\n\n## Changes we're making\n\nWe are revising our monitoring approaches to identify and address service disruptions proactively, while also improving our communication processes to ensure timely and accurate customer updates.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2025-10-23T21:40:49.301-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2025-10-23T21:12:13.320-07:00",
api/v/packet.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "packet",
4
  "platform": "statuspage",
5
  "status_url": "http://status.packet.net",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "critical",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-08-17T17:10:44.803Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-17T15:38:05.971Z",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-06-30T05:21:34.880Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-06-30T03:59:40.436Z",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-06-25T02:08:14.894Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-06-25T00:11:31.243Z",
@@ -51,7 +51,7 @@
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "none",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-05-10T23:35:00.046Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-05-09T06:10:01.000Z",
@@ -64,7 +64,7 @@
64
  "body": "At this time the device has recovered and MLAG bonds have been restored. The device has fully recovered, and all services are currently operating normally.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-04-14T16:48:11.553Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-04-14T16:25:44.586Z",
@@ -77,7 +77,7 @@
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-04-06T08:23:46.448Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-04-06T08:16:52.259Z",
@@ -90,7 +90,7 @@
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "major",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-02-06T13:47:50.204Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-02-06T12:34:05.765Z",
@@ -103,7 +103,7 @@
103
  "body": "Our monitoring systems detected DDoS attack patterns in SV metro (1200 - 1204 UTC) and DC metro (1208 - 1211 UTC) which caused brief period of packet loss while mitigation measures were activated. Traffic levels then stabilized to normal levels.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "none",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-01-28T16:33:23.646Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-01-28T16:33:23.587Z",
@@ -116,7 +116,7 @@
116
  "body": "This incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-01-22T13:11:54.205Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-01-22T11:07:05.274Z",
@@ -129,7 +129,7 @@
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "none",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-01-21T14:34:07.046Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-01-21T12:20:44.988Z",
@@ -142,7 +142,7 @@
142
  "body": "This incident has been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "none",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2026-01-20T23:55:45.402Z",
147
  "resolved_inferred": false,
148
  "started_at": "2026-01-20T23:38:09.339Z",
@@ -155,7 +155,7 @@
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "critical",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2026-01-15T08:04:29.912Z",
160
  "resolved_inferred": false,
161
  "started_at": "2026-01-15T07:05:15.182Z",
@@ -168,7 +168,7 @@
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "none",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2025-12-23T17:14:34.654Z",
173
  "resolved_inferred": false,
174
  "started_at": "2025-12-23T16:14:54.970Z",
@@ -181,7 +181,7 @@
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "none",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2025-12-19T10:01:09.404Z",
186
  "resolved_inferred": false,
187
  "started_at": "2025-12-19T07:57:11.513Z",
@@ -194,7 +194,7 @@
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2025-12-02T04:08:17.308Z",
199
  "resolved_inferred": false,
200
  "started_at": "2025-12-02T02:47:51.959Z",
@@ -207,7 +207,7 @@
207
  "body": "This incident has been resolved.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "critical",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2025-11-18T19:51:33.887Z",
212
  "resolved_inferred": false,
213
  "started_at": "2025-11-18T14:26:05.876Z",
@@ -220,7 +220,7 @@
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2025-11-14T12:51:24.098Z",
225
  "resolved_inferred": false,
226
  "started_at": "2025-11-14T12:04:44.887Z",
@@ -233,7 +233,7 @@
233
  "body": "All services remain stable and the the issue is deemed resolved. Root cause analysis is ongoing.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2025-10-21T15:03:52.083Z",
238
  "resolved_inferred": false,
239
  "started_at": "2025-10-21T10:59:05.000Z",
@@ -246,7 +246,7 @@
246
  "body": "This incident has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2025-10-17T13:53:19.000Z",
251
  "resolved_inferred": false,
252
  "started_at": "2025-10-17T13:12:40.000Z",
@@ -259,7 +259,7 @@
259
  "body": "This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "none",
262
- "last_seen": "2026-09-04T12:24:18Z",
263
  "resolved_at": "2025-10-16T20:01:08.548Z",
264
  "resolved_inferred": false,
265
  "started_at": "2025-10-16T18:55:06.090Z",
@@ -272,7 +272,7 @@
272
  "body": "This incident has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "minor",
275
- "last_seen": "2026-09-04T12:24:18Z",
276
  "resolved_at": "2025-10-11T04:16:27.138Z",
277
  "resolved_inferred": false,
278
  "started_at": "2025-10-11T00:27:10.342Z",
@@ -285,7 +285,7 @@
285
  "body": "This incident has been resolved.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "minor",
288
- "last_seen": "2026-09-04T12:24:18Z",
289
  "resolved_at": "2025-09-30T08:55:07.430Z",
290
  "resolved_inferred": false,
291
  "started_at": "2025-09-30T02:07:58.054Z",
@@ -298,7 +298,7 @@
298
  "body": "This incident has been resolved.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "none",
301
- "last_seen": "2026-09-04T12:24:18Z",
302
  "resolved_at": "2025-09-23T21:50:00.944Z",
303
  "resolved_inferred": false,
304
  "started_at": "2025-09-23T20:56:02.418Z",
@@ -311,7 +311,7 @@
311
  "body": "This incident has been resolved.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "minor",
314
- "last_seen": "2026-09-04T12:24:18Z",
315
  "resolved_at": "2025-09-23T04:15:56.479Z",
316
  "resolved_inferred": false,
317
  "started_at": "2025-09-23T02:34:32.891Z",
@@ -324,7 +324,7 @@
324
  "body": "This incident has been resolved.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "none",
327
- "last_seen": "2026-09-04T12:24:18Z",
328
  "resolved_at": "2025-09-19T19:44:00.240Z",
329
  "resolved_inferred": false,
330
  "started_at": "2025-09-19T18:56:13.306Z",
@@ -337,7 +337,7 @@
337
  "body": "This incident has been resolved.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "none",
340
- "last_seen": "2026-09-04T12:24:18Z",
341
  "resolved_at": "2025-09-19T05:48:04.814Z",
342
  "resolved_inferred": false,
343
  "started_at": "2025-09-19T05:19:35.393Z",
@@ -350,7 +350,7 @@
350
  "body": "At approximately 18:24 UTC on September 3rd 2025, customers in the Sao Paulo metro may have experienced temporary loss of connectivity. This issue was due to a third party circuit outage. Customer traffic was restored at approximately 18:26 UTC. \n\nIf you have any questions please contact support@equinixmetal.com",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "none",
353
- "last_seen": "2026-09-04T12:24:18Z",
354
  "resolved_at": "2025-09-03T22:24:00.000Z",
355
  "resolved_inferred": false,
356
  "started_at": "2025-09-03T18:46:54.087Z",
@@ -363,7 +363,7 @@
363
  "body": "This incident has been resolved.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "minor",
366
- "last_seen": "2026-09-04T12:24:18Z",
367
  "resolved_at": "2025-08-28T06:47:10.823Z",
368
  "resolved_inferred": false,
369
  "started_at": "2025-08-28T02:19:34.928Z",
@@ -376,7 +376,7 @@
376
  "body": "At approximately 12:15 UTC on August 27th 2025, customers in the Singapore metro may have experienced temporary loss of connectivity. This issue was due to a third party circuit outage. Customer traffic was restored at approximately 12:19 UTC. \n\nIf you have any questions please contact support@equinixmetal.com",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "none",
379
- "last_seen": "2026-09-04T12:24:18Z",
380
  "resolved_at": "2025-08-27T04:15:00.000Z",
381
  "resolved_inferred": false,
382
  "started_at": "2025-08-27T04:15:00.000Z",
@@ -389,7 +389,7 @@
389
  "body": "This incident has been resolved.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "none",
392
- "last_seen": "2026-09-04T12:24:18Z",
393
  "resolved_at": "2025-08-22T12:25:57.414Z",
394
  "resolved_inferred": false,
395
  "started_at": "2025-08-22T10:38:42.953Z",
@@ -402,7 +402,7 @@
402
  "body": "This incident has been resolved.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "minor",
405
- "last_seen": "2026-09-04T12:24:18Z",
406
  "resolved_at": "2025-08-08T16:04:51.688Z",
407
  "resolved_inferred": false,
408
  "started_at": "2025-08-08T15:07:47.795Z",
@@ -415,7 +415,7 @@
415
  "body": "This incident has been resolved.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "none",
418
- "last_seen": "2026-09-04T12:24:18Z",
419
  "resolved_at": "2025-08-08T08:50:24.702Z",
420
  "resolved_inferred": false,
421
  "started_at": "2025-08-08T07:39:17.000Z",
 
3
  "slug": "packet",
4
  "platform": "statuspage",
5
  "status_url": "http://status.packet.net",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "critical",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-08-17T17:10:44.803Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-17T15:38:05.971Z",
 
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-06-30T05:21:34.880Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-06-30T03:59:40.436Z",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-06-25T02:08:14.894Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-06-25T00:11:31.243Z",
 
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "none",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-05-10T23:35:00.046Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-05-09T06:10:01.000Z",
 
64
  "body": "At this time the device has recovered and MLAG bonds have been restored. The device has fully recovered, and all services are currently operating normally.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-04-14T16:48:11.553Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-04-14T16:25:44.586Z",
 
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-04-06T08:23:46.448Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-04-06T08:16:52.259Z",
 
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "major",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-02-06T13:47:50.204Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-02-06T12:34:05.765Z",
 
103
  "body": "Our monitoring systems detected DDoS attack patterns in SV metro (1200 - 1204 UTC) and DC metro (1208 - 1211 UTC) which caused brief period of packet loss while mitigation measures were activated. Traffic levels then stabilized to normal levels.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "none",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-01-28T16:33:23.646Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-01-28T16:33:23.587Z",
 
116
  "body": "This incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-01-22T13:11:54.205Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-01-22T11:07:05.274Z",
 
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "none",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-01-21T14:34:07.046Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-01-21T12:20:44.988Z",
 
142
  "body": "This incident has been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "none",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2026-01-20T23:55:45.402Z",
147
  "resolved_inferred": false,
148
  "started_at": "2026-01-20T23:38:09.339Z",
 
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "critical",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2026-01-15T08:04:29.912Z",
160
  "resolved_inferred": false,
161
  "started_at": "2026-01-15T07:05:15.182Z",
 
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "none",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2025-12-23T17:14:34.654Z",
173
  "resolved_inferred": false,
174
  "started_at": "2025-12-23T16:14:54.970Z",
 
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "none",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2025-12-19T10:01:09.404Z",
186
  "resolved_inferred": false,
187
  "started_at": "2025-12-19T07:57:11.513Z",
 
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2025-12-02T04:08:17.308Z",
199
  "resolved_inferred": false,
200
  "started_at": "2025-12-02T02:47:51.959Z",
 
207
  "body": "This incident has been resolved.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "critical",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2025-11-18T19:51:33.887Z",
212
  "resolved_inferred": false,
213
  "started_at": "2025-11-18T14:26:05.876Z",
 
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2025-11-14T12:51:24.098Z",
225
  "resolved_inferred": false,
226
  "started_at": "2025-11-14T12:04:44.887Z",
 
233
  "body": "All services remain stable and the the issue is deemed resolved. Root cause analysis is ongoing.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2025-10-21T15:03:52.083Z",
238
  "resolved_inferred": false,
239
  "started_at": "2025-10-21T10:59:05.000Z",
 
246
  "body": "This incident has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2025-10-17T13:53:19.000Z",
251
  "resolved_inferred": false,
252
  "started_at": "2025-10-17T13:12:40.000Z",
 
259
  "body": "This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "none",
262
+ "last_seen": "2026-09-04T14:19:03Z",
263
  "resolved_at": "2025-10-16T20:01:08.548Z",
264
  "resolved_inferred": false,
265
  "started_at": "2025-10-16T18:55:06.090Z",
 
272
  "body": "This incident has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "minor",
275
+ "last_seen": "2026-09-04T14:19:03Z",
276
  "resolved_at": "2025-10-11T04:16:27.138Z",
277
  "resolved_inferred": false,
278
  "started_at": "2025-10-11T00:27:10.342Z",
 
285
  "body": "This incident has been resolved.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "minor",
288
+ "last_seen": "2026-09-04T14:19:03Z",
289
  "resolved_at": "2025-09-30T08:55:07.430Z",
290
  "resolved_inferred": false,
291
  "started_at": "2025-09-30T02:07:58.054Z",
 
298
  "body": "This incident has been resolved.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "none",
301
+ "last_seen": "2026-09-04T14:19:03Z",
302
  "resolved_at": "2025-09-23T21:50:00.944Z",
303
  "resolved_inferred": false,
304
  "started_at": "2025-09-23T20:56:02.418Z",
 
311
  "body": "This incident has been resolved.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "minor",
314
+ "last_seen": "2026-09-04T14:19:03Z",
315
  "resolved_at": "2025-09-23T04:15:56.479Z",
316
  "resolved_inferred": false,
317
  "started_at": "2025-09-23T02:34:32.891Z",
 
324
  "body": "This incident has been resolved.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "none",
327
+ "last_seen": "2026-09-04T14:19:03Z",
328
  "resolved_at": "2025-09-19T19:44:00.240Z",
329
  "resolved_inferred": false,
330
  "started_at": "2025-09-19T18:56:13.306Z",
 
337
  "body": "This incident has been resolved.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "none",
340
+ "last_seen": "2026-09-04T14:19:03Z",
341
  "resolved_at": "2025-09-19T05:48:04.814Z",
342
  "resolved_inferred": false,
343
  "started_at": "2025-09-19T05:19:35.393Z",
 
350
  "body": "At approximately 18:24 UTC on September 3rd 2025, customers in the Sao Paulo metro may have experienced temporary loss of connectivity. This issue was due to a third party circuit outage. Customer traffic was restored at approximately 18:26 UTC. \n\nIf you have any questions please contact support@equinixmetal.com",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "none",
353
+ "last_seen": "2026-09-04T14:19:03Z",
354
  "resolved_at": "2025-09-03T22:24:00.000Z",
355
  "resolved_inferred": false,
356
  "started_at": "2025-09-03T18:46:54.087Z",
 
363
  "body": "This incident has been resolved.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "minor",
366
+ "last_seen": "2026-09-04T14:19:03Z",
367
  "resolved_at": "2025-08-28T06:47:10.823Z",
368
  "resolved_inferred": false,
369
  "started_at": "2025-08-28T02:19:34.928Z",
 
376
  "body": "At approximately 12:15 UTC on August 27th 2025, customers in the Singapore metro may have experienced temporary loss of connectivity. This issue was due to a third party circuit outage. Customer traffic was restored at approximately 12:19 UTC. \n\nIf you have any questions please contact support@equinixmetal.com",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "none",
379
+ "last_seen": "2026-09-04T14:19:03Z",
380
  "resolved_at": "2025-08-27T04:15:00.000Z",
381
  "resolved_inferred": false,
382
  "started_at": "2025-08-27T04:15:00.000Z",
 
389
  "body": "This incident has been resolved.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "none",
392
+ "last_seen": "2026-09-04T14:19:03Z",
393
  "resolved_at": "2025-08-22T12:25:57.414Z",
394
  "resolved_inferred": false,
395
  "started_at": "2025-08-22T10:38:42.953Z",
 
402
  "body": "This incident has been resolved.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "minor",
405
+ "last_seen": "2026-09-04T14:19:03Z",
406
  "resolved_at": "2025-08-08T16:04:51.688Z",
407
  "resolved_inferred": false,
408
  "started_at": "2025-08-08T15:07:47.795Z",
 
415
  "body": "This incident has been resolved.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "none",
418
+ "last_seen": "2026-09-04T14:19:03Z",
419
  "resolved_at": "2025-08-08T08:50:24.702Z",
420
  "resolved_inferred": false,
421
  "started_at": "2025-08-08T07:39:17.000Z",
api/v/pairsoft.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "pairsoft",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pairsoft.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2025-11-17T16:04:14.564-05:00",
17
  "resolved_inferred": false,
18
  "started_at": "2025-11-17T10:46:17.758-05:00",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "none",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2025-10-30T09:03:01.366-04:00",
30
  "resolved_inferred": false,
31
  "started_at": "2025-10-29T12:50:19.840-04:00",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2025-09-29T12:56:05.910-04:00",
43
  "resolved_inferred": false,
44
  "started_at": "2025-09-29T12:04:14.703-04:00",
 
3
  "slug": "pairsoft",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pairsoft.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2025-11-17T16:04:14.564-05:00",
17
  "resolved_inferred": false,
18
  "started_at": "2025-11-17T10:46:17.758-05:00",
 
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "none",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2025-10-30T09:03:01.366-04:00",
30
  "resolved_inferred": false,
31
  "started_at": "2025-10-29T12:50:19.840-04:00",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2025-09-29T12:56:05.910-04:00",
43
  "resolved_inferred": false,
44
  "started_at": "2025-09-29T12:04:14.703-04:00",
api/v/pantheon.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "pantheon",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pantheon.io",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-09-03T12:41:34.113-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-03T11:23:52.491-07:00",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "critical",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-09-01T13:37:12.467-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-09-01T08:14:31.418-07:00",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-08-20T15:26:52.682-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-08-20T14:16:49.411-07:00",
@@ -51,7 +51,7 @@
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-08-18T15:47:14.493-07:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-08-18T08:35:03.460-07:00",
@@ -64,7 +64,7 @@
64
  "body": "We have concluded our monitoring period and have deemed this incident resolved. Thank you for your patience.\n\nIf you encounter any further issues, please open a ticket with us at helpdesk@pantheon.io.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-08-18T04:03:19.527-07:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-08-18T00:05:18.370-07:00",
@@ -77,7 +77,7 @@
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-08-07T15:08:38.756-07:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-08-07T04:04:26.007-07:00",
@@ -90,7 +90,7 @@
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-08-06T14:59:57.323-07:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-08-06T12:36:48.201-07:00",
@@ -103,7 +103,7 @@
103
  "body": "This incident has been resolved, and full performance has been restored to the Dashboard, Workflow Operations, and Terminus Operations. Live hosted sites and uptime remained fully operational throughout this event.\n\nThank you for your patience while we worked to resolve this. If you encounter any further issues, please contact our Support team.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-08-06T10:11:54.924-07:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-08-04T11:37:11.820-07:00",
@@ -116,7 +116,7 @@
116
  "body": "This incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "critical",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-07-30T07:43:22.625-07:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-07-30T06:25:20.328-07:00",
@@ -129,7 +129,7 @@
129
  "body": "This incident has been resolved. Google login option is now working as expected\n\nThank you for your patience.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-07-27T04:49:55.605-07:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-07-27T00:33:49.549-07:00",
@@ -142,7 +142,7 @@
142
  "body": "This incident has been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "minor",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2026-07-24T09:20:50.166-07:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-07-24T07:21:36.927-07:00",
@@ -155,7 +155,7 @@
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "major",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2026-07-22T03:27:23.844-07:00",
160
  "resolved_inferred": false,
161
  "started_at": "2026-07-20T14:09:52.414-07:00",
@@ -168,7 +168,7 @@
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2026-07-21T14:33:38.248-07:00",
173
  "resolved_inferred": false,
174
  "started_at": "2026-07-20T12:26:50.227-07:00",
@@ -181,7 +181,7 @@
181
  "body": "This incident has been resolved. The Pantheon Dashboard is performing normally, and loading times remain completely stable.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "minor",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2026-07-11T14:33:29.552-07:00",
186
  "resolved_inferred": false,
187
  "started_at": "2026-07-10T09:33:26.005-07:00",
@@ -194,7 +194,7 @@
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "critical",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2026-07-03T07:00:06.433-07:00",
199
  "resolved_inferred": false,
200
  "started_at": "2026-07-02T23:50:34.086-07:00",
@@ -207,7 +207,7 @@
207
  "body": "This incident has been resolved. The Pantheon Dashboard is performing normally, and loading times remain completely stable.\n\nThank you for your patience while we worked to resolve this issue. If you experience any further difficulties, please contact us directly at helpdesk@pantheon.io.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "minor",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2026-07-01T11:49:40.445-07:00",
212
  "resolved_inferred": false,
213
  "started_at": "2026-06-30T11:15:04.566-07:00",
@@ -220,7 +220,7 @@
220
  "body": "Our Engineering team has verified that all platform services are fully restored and stable. The Pantheon Dashboard is performing normally, and all background workflows are processing successfully without any lingering delays.\n\nThe underlying issue has been completely mitigated, and we have concluded our monitoring period. Thank you for your patience while we worked to resolve this.\n\nIf you encounter any further issues, please open a ticket with us at helpdesk@pantheon.io.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2026-06-10T05:07:32.461-07:00",
225
  "resolved_inferred": false,
226
  "started_at": "2026-06-09T23:34:47.770-07:00",
@@ -233,7 +233,7 @@
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "minor",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2026-05-27T22:40:11.501-07:00",
238
  "resolved_inferred": false,
239
  "started_at": "2026-05-27T11:13:21.746-07:00",
@@ -246,7 +246,7 @@
246
  "body": "This incident has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2026-05-27T14:59:56.599-07:00",
251
  "resolved_inferred": false,
252
  "started_at": "2026-05-27T09:22:23.000-07:00",
@@ -259,7 +259,7 @@
259
  "body": "This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "minor",
262
- "last_seen": "2026-09-04T12:24:18Z",
263
  "resolved_at": "2026-05-25T13:39:24.069-07:00",
264
  "resolved_inferred": false,
265
  "started_at": "2026-05-25T08:53:32.501-07:00",
@@ -272,7 +272,7 @@
272
  "body": "This incident has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "minor",
275
- "last_seen": "2026-09-04T12:24:18Z",
276
  "resolved_at": "2026-05-20T16:26:19.825-07:00",
277
  "resolved_inferred": false,
278
  "started_at": "2026-05-20T12:26:44.269-07:00",
@@ -285,7 +285,7 @@
285
  "body": "This incident has been resolved.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "minor",
288
- "last_seen": "2026-09-04T12:24:18Z",
289
  "resolved_at": "2026-05-13T15:42:48.075-07:00",
290
  "resolved_inferred": false,
291
  "started_at": "2026-05-13T08:20:01.516-07:00",
@@ -298,7 +298,7 @@
298
  "body": "This incident has been resolved.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "minor",
301
- "last_seen": "2026-09-04T12:24:18Z",
302
  "resolved_at": "2026-05-05T12:33:56.151-07:00",
303
  "resolved_inferred": false,
304
  "started_at": "2026-05-05T09:09:11.059-07:00",
@@ -311,7 +311,7 @@
311
  "body": "This incident has been resolved.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "major",
314
- "last_seen": "2026-09-04T12:24:18Z",
315
  "resolved_at": "2026-04-24T07:45:11.357-07:00",
316
  "resolved_inferred": false,
317
  "started_at": "2026-04-23T23:21:46.787-07:00",
@@ -324,7 +324,7 @@
324
  "body": "This incident has been resolved. You can now safely proceed with deployments.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "major",
327
- "last_seen": "2026-09-04T12:24:18Z",
328
  "resolved_at": "2026-04-18T19:00:30.726-07:00",
329
  "resolved_inferred": false,
330
  "started_at": "2026-04-18T17:03:39.775-07:00",
@@ -337,7 +337,7 @@
337
  "body": "Final Update: We have concluded our investigation into the reports of unauthorized account access. Our team has worked directly with the small number of affected customers to secure their accounts and remediate any unauthorized changes.\n\nMonitoring & Conclusion: We have seen no further evidence of unauthorized activity related to this incident. Our systems remain secure, and we continue to monitor for suspicious login patterns.\n\nOngoing Security Best Practices: While this incident is resolved, credential stuffing remains a common web-wide threat. To keep your account secure, we strongly recommend:\n\n\u2022 Enabling MFA on all Pantheon user accounts.\n\u2022 Using unique passwords managed via a password manager.\n\u2022 Rotating secrets/keys if you suspect your local environment has been compromised.\n\nThank you for your patience as we worked to keep the Pantheon community secure.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "none",
340
- "last_seen": "2026-09-04T12:24:18Z",
341
  "resolved_at": "2026-04-16T13:30:53.991-07:00",
342
  "resolved_inferred": false,
343
  "started_at": "2026-04-15T07:27:54.000-07:00",
@@ -350,7 +350,7 @@
350
  "body": "This incident has been resolved.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "major",
353
- "last_seen": "2026-09-04T12:24:18Z",
354
  "resolved_at": "2026-04-16T07:47:49.418-07:00",
355
  "resolved_inferred": false,
356
  "started_at": "2026-04-15T03:40:19.117-07:00",
@@ -363,7 +363,7 @@
363
  "body": "This incident is resolved and the Pantheon platform is operating normally. Our engineering team confirms stability across the platform. We are actively improving the system against future incidents.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "minor",
366
- "last_seen": "2026-09-04T12:24:18Z",
367
  "resolved_at": "2026-04-03T14:46:05.016-07:00",
368
  "resolved_inferred": false,
369
  "started_at": "2026-03-30T03:22:20.415-07:00",
@@ -376,7 +376,7 @@
376
  "body": "This incident has been resolved.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "minor",
379
- "last_seen": "2026-09-04T12:24:18Z",
380
  "resolved_at": "2026-03-28T07:30:33.426-07:00",
381
  "resolved_inferred": false,
382
  "started_at": "2026-03-28T05:41:54.985-07:00",
@@ -389,7 +389,7 @@
389
  "body": "This incident has been resolved. All Dashboard and Terminus operations are operational now.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "minor",
392
- "last_seen": "2026-09-04T12:24:18Z",
393
  "resolved_at": "2026-03-27T16:41:31.878-07:00",
394
  "resolved_inferred": false,
395
  "started_at": "2026-03-26T05:22:53.179-07:00",
@@ -402,7 +402,7 @@
402
  "body": "This incident has been resolved.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "minor",
405
- "last_seen": "2026-09-04T12:24:18Z",
406
  "resolved_at": "2026-03-17T18:43:40.634-07:00",
407
  "resolved_inferred": false,
408
  "started_at": "2026-03-11T08:49:25.655-07:00",
@@ -415,7 +415,7 @@
415
  "body": "This incident has been resolved.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "minor",
418
- "last_seen": "2026-09-04T12:24:18Z",
419
  "resolved_at": "2026-03-09T07:11:53.207-07:00",
420
  "resolved_inferred": false,
421
  "started_at": "2026-03-08T17:30:22.821-07:00",
@@ -428,7 +428,7 @@
428
  "body": "This incident has been resolved.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "minor",
431
- "last_seen": "2026-09-04T12:24:18Z",
432
  "resolved_at": "2026-02-22T19:05:12.180-08:00",
433
  "resolved_inferred": false,
434
  "started_at": "2026-02-22T15:57:19.068-08:00",
@@ -441,7 +441,7 @@
441
  "body": "This incident has been resolved.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "minor",
444
- "last_seen": "2026-09-04T12:24:18Z",
445
  "resolved_at": "2026-02-10T14:07:43.430-08:00",
446
  "resolved_inferred": false,
447
  "started_at": "2026-02-10T13:07:26.548-08:00",
@@ -454,7 +454,7 @@
454
  "body": "This incident has been resolved.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "minor",
457
- "last_seen": "2026-09-04T12:24:18Z",
458
  "resolved_at": "2026-02-09T10:56:17.885-08:00",
459
  "resolved_inferred": false,
460
  "started_at": "2026-02-09T09:31:51.082-08:00",
@@ -467,7 +467,7 @@
467
  "body": "This incident has been resolved, and the Dashboard has returned to normal operation.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "minor",
470
- "last_seen": "2026-09-04T12:24:18Z",
471
  "resolved_at": "2026-02-04T11:34:04.489-08:00",
472
  "resolved_inferred": false,
473
  "started_at": "2026-02-04T10:17:51.231-08:00",
@@ -480,7 +480,7 @@
480
  "body": "This incident has been resolved. Thank you for your patience. Secure Integration is now working as expected.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "minor",
483
- "last_seen": "2026-09-04T12:24:18Z",
484
  "resolved_at": "2026-01-29T16:31:46.213-08:00",
485
  "resolved_inferred": false,
486
  "started_at": "2026-01-29T15:49:41.947-08:00",
@@ -493,7 +493,7 @@
493
  "body": "This incident has been resolved.",
494
  "first_seen": "2026-09-04T07:06:16Z",
495
  "impact": "minor",
496
- "last_seen": "2026-09-04T12:24:18Z",
497
  "resolved_at": "2026-01-29T17:38:32.696-08:00",
498
  "resolved_inferred": false,
499
  "started_at": "2026-01-29T09:01:25.661-08:00",
@@ -506,7 +506,7 @@
506
  "body": "This incident has been resolved.",
507
  "first_seen": "2026-09-04T07:06:16Z",
508
  "impact": "minor",
509
- "last_seen": "2026-09-04T12:24:18Z",
510
  "resolved_at": "2025-12-10T00:55:04.038-08:00",
511
  "resolved_inferred": false,
512
  "started_at": "2025-12-09T22:52:59.837-08:00",
@@ -519,7 +519,7 @@
519
  "body": "This incident has been resolved, and the Dashboard is now functioning as expected. \n\nIf you experience any further issues, please don\u2019t hesitate to let us know through support chats or by opening a ticket.",
520
  "first_seen": "2026-09-04T07:06:16Z",
521
  "impact": "minor",
522
- "last_seen": "2026-09-04T12:24:18Z",
523
  "resolved_at": "2025-12-09T12:52:29.539-08:00",
524
  "resolved_inferred": false,
525
  "started_at": "2025-12-09T09:48:07.574-08:00",
@@ -532,7 +532,7 @@
532
  "body": "This incident has been resolved.",
533
  "first_seen": "2026-09-04T07:06:16Z",
534
  "impact": "minor",
535
- "last_seen": "2026-09-04T12:24:18Z",
536
  "resolved_at": "2025-12-02T12:24:25.773-08:00",
537
  "resolved_inferred": false,
538
  "started_at": "2025-12-02T11:08:32.865-08:00",
@@ -545,7 +545,7 @@
545
  "body": "This incident has been resolved.",
546
  "first_seen": "2026-09-04T07:06:16Z",
547
  "impact": "minor",
548
- "last_seen": "2026-09-04T12:24:18Z",
549
  "resolved_at": "2025-11-18T15:11:05.335-08:00",
550
  "resolved_inferred": false,
551
  "started_at": "2025-11-18T12:09:26.067-08:00",
@@ -558,7 +558,7 @@
558
  "body": "This incident has been resolved.",
559
  "first_seen": "2026-09-04T07:06:16Z",
560
  "impact": "minor",
561
- "last_seen": "2026-09-04T12:24:18Z",
562
  "resolved_at": "2025-10-28T03:33:47.990-07:00",
563
  "resolved_inferred": false,
564
  "started_at": "2025-10-27T03:13:57.108-07:00",
@@ -571,7 +571,7 @@
571
  "body": "This incident has been resolved. Dashboard Operations are back to normal.",
572
  "first_seen": "2026-09-04T07:06:16Z",
573
  "impact": "minor",
574
- "last_seen": "2026-09-04T12:24:18Z",
575
  "resolved_at": "2025-10-14T23:51:48.035-07:00",
576
  "resolved_inferred": false,
577
  "started_at": "2025-10-14T21:53:10.704-07:00",
@@ -584,7 +584,7 @@
584
  "body": "This incident has been resolved. Dashboard operations are back to normal. Thank you for your patience throughout the process.",
585
  "first_seen": "2026-09-04T07:06:16Z",
586
  "impact": "minor",
587
- "last_seen": "2026-09-04T12:24:18Z",
588
  "resolved_at": "2025-10-08T19:48:51.447-07:00",
589
  "resolved_inferred": false,
590
  "started_at": "2025-10-08T17:52:43.577-07:00",
@@ -597,7 +597,7 @@
597
  "body": "This incident has been resolved.",
598
  "first_seen": "2026-09-04T07:06:16Z",
599
  "impact": "minor",
600
- "last_seen": "2026-09-04T12:24:18Z",
601
  "resolved_at": "2025-10-02T16:40:09.146-07:00",
602
  "resolved_inferred": false,
603
  "started_at": "2025-10-01T10:19:59.119-07:00",
@@ -610,7 +610,7 @@
610
  "body": "This incident has been resolved.",
611
  "first_seen": "2026-09-04T07:06:16Z",
612
  "impact": "minor",
613
- "last_seen": "2026-09-04T12:24:18Z",
614
  "resolved_at": "2025-09-18T03:14:12.026-07:00",
615
  "resolved_inferred": false,
616
  "started_at": "2025-09-15T14:09:33.787-07:00",
@@ -623,7 +623,7 @@
623
  "body": "This incident has been resolved.",
624
  "first_seen": "2026-09-04T07:06:16Z",
625
  "impact": "minor",
626
- "last_seen": "2026-09-04T12:24:18Z",
627
  "resolved_at": "2025-09-15T07:12:45.294-07:00",
628
  "resolved_inferred": false,
629
  "started_at": "2025-09-15T02:53:49.386-07:00",
@@ -636,7 +636,7 @@
636
  "body": "This incident has been resolved.",
637
  "first_seen": "2026-09-04T07:06:16Z",
638
  "impact": "minor",
639
- "last_seen": "2026-09-04T12:24:18Z",
640
  "resolved_at": "2025-09-10T17:40:05.590-07:00",
641
  "resolved_inferred": false,
642
  "started_at": "2025-09-10T17:00:08.750-07:00",
@@ -649,7 +649,7 @@
649
  "body": "The analysis of final vendor logs produced no additional information or signs of compromise.",
650
  "first_seen": "2026-09-04T07:06:16Z",
651
  "impact": "maintenance",
652
- "last_seen": "2026-09-04T12:24:18Z",
653
  "resolved_at": "2025-09-26T14:55:58.430-07:00",
654
  "resolved_inferred": false,
655
  "started_at": "2025-09-05T13:50:36.000-07:00",
 
3
  "slug": "pantheon",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pantheon.io",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-09-03T12:41:34.113-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-03T11:23:52.491-07:00",
 
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "critical",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-09-01T13:37:12.467-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-09-01T08:14:31.418-07:00",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-08-20T15:26:52.682-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-08-20T14:16:49.411-07:00",
 
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-08-18T15:47:14.493-07:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-08-18T08:35:03.460-07:00",
 
64
  "body": "We have concluded our monitoring period and have deemed this incident resolved. Thank you for your patience.\n\nIf you encounter any further issues, please open a ticket with us at helpdesk@pantheon.io.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-08-18T04:03:19.527-07:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-08-18T00:05:18.370-07:00",
 
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-08-07T15:08:38.756-07:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-08-07T04:04:26.007-07:00",
 
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-08-06T14:59:57.323-07:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-08-06T12:36:48.201-07:00",
 
103
  "body": "This incident has been resolved, and full performance has been restored to the Dashboard, Workflow Operations, and Terminus Operations. Live hosted sites and uptime remained fully operational throughout this event.\n\nThank you for your patience while we worked to resolve this. If you encounter any further issues, please contact our Support team.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-08-06T10:11:54.924-07:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-08-04T11:37:11.820-07:00",
 
116
  "body": "This incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "critical",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-07-30T07:43:22.625-07:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-07-30T06:25:20.328-07:00",
 
129
  "body": "This incident has been resolved. Google login option is now working as expected\n\nThank you for your patience.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-07-27T04:49:55.605-07:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-07-27T00:33:49.549-07:00",
 
142
  "body": "This incident has been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "minor",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2026-07-24T09:20:50.166-07:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-07-24T07:21:36.927-07:00",
 
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "major",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2026-07-22T03:27:23.844-07:00",
160
  "resolved_inferred": false,
161
  "started_at": "2026-07-20T14:09:52.414-07:00",
 
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2026-07-21T14:33:38.248-07:00",
173
  "resolved_inferred": false,
174
  "started_at": "2026-07-20T12:26:50.227-07:00",
 
181
  "body": "This incident has been resolved. The Pantheon Dashboard is performing normally, and loading times remain completely stable.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "minor",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2026-07-11T14:33:29.552-07:00",
186
  "resolved_inferred": false,
187
  "started_at": "2026-07-10T09:33:26.005-07:00",
 
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "critical",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2026-07-03T07:00:06.433-07:00",
199
  "resolved_inferred": false,
200
  "started_at": "2026-07-02T23:50:34.086-07:00",
 
207
  "body": "This incident has been resolved. The Pantheon Dashboard is performing normally, and loading times remain completely stable.\n\nThank you for your patience while we worked to resolve this issue. If you experience any further difficulties, please contact us directly at helpdesk@pantheon.io.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "minor",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2026-07-01T11:49:40.445-07:00",
212
  "resolved_inferred": false,
213
  "started_at": "2026-06-30T11:15:04.566-07:00",
 
220
  "body": "Our Engineering team has verified that all platform services are fully restored and stable. The Pantheon Dashboard is performing normally, and all background workflows are processing successfully without any lingering delays.\n\nThe underlying issue has been completely mitigated, and we have concluded our monitoring period. Thank you for your patience while we worked to resolve this.\n\nIf you encounter any further issues, please open a ticket with us at helpdesk@pantheon.io.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2026-06-10T05:07:32.461-07:00",
225
  "resolved_inferred": false,
226
  "started_at": "2026-06-09T23:34:47.770-07:00",
 
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "minor",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2026-05-27T22:40:11.501-07:00",
238
  "resolved_inferred": false,
239
  "started_at": "2026-05-27T11:13:21.746-07:00",
 
246
  "body": "This incident has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2026-05-27T14:59:56.599-07:00",
251
  "resolved_inferred": false,
252
  "started_at": "2026-05-27T09:22:23.000-07:00",
 
259
  "body": "This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "minor",
262
+ "last_seen": "2026-09-04T14:19:03Z",
263
  "resolved_at": "2026-05-25T13:39:24.069-07:00",
264
  "resolved_inferred": false,
265
  "started_at": "2026-05-25T08:53:32.501-07:00",
 
272
  "body": "This incident has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "minor",
275
+ "last_seen": "2026-09-04T14:19:03Z",
276
  "resolved_at": "2026-05-20T16:26:19.825-07:00",
277
  "resolved_inferred": false,
278
  "started_at": "2026-05-20T12:26:44.269-07:00",
 
285
  "body": "This incident has been resolved.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "minor",
288
+ "last_seen": "2026-09-04T14:19:03Z",
289
  "resolved_at": "2026-05-13T15:42:48.075-07:00",
290
  "resolved_inferred": false,
291
  "started_at": "2026-05-13T08:20:01.516-07:00",
 
298
  "body": "This incident has been resolved.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "minor",
301
+ "last_seen": "2026-09-04T14:19:03Z",
302
  "resolved_at": "2026-05-05T12:33:56.151-07:00",
303
  "resolved_inferred": false,
304
  "started_at": "2026-05-05T09:09:11.059-07:00",
 
311
  "body": "This incident has been resolved.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "major",
314
+ "last_seen": "2026-09-04T14:19:03Z",
315
  "resolved_at": "2026-04-24T07:45:11.357-07:00",
316
  "resolved_inferred": false,
317
  "started_at": "2026-04-23T23:21:46.787-07:00",
 
324
  "body": "This incident has been resolved. You can now safely proceed with deployments.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "major",
327
+ "last_seen": "2026-09-04T14:19:03Z",
328
  "resolved_at": "2026-04-18T19:00:30.726-07:00",
329
  "resolved_inferred": false,
330
  "started_at": "2026-04-18T17:03:39.775-07:00",
 
337
  "body": "Final Update: We have concluded our investigation into the reports of unauthorized account access. Our team has worked directly with the small number of affected customers to secure their accounts and remediate any unauthorized changes.\n\nMonitoring & Conclusion: We have seen no further evidence of unauthorized activity related to this incident. Our systems remain secure, and we continue to monitor for suspicious login patterns.\n\nOngoing Security Best Practices: While this incident is resolved, credential stuffing remains a common web-wide threat. To keep your account secure, we strongly recommend:\n\n\u2022 Enabling MFA on all Pantheon user accounts.\n\u2022 Using unique passwords managed via a password manager.\n\u2022 Rotating secrets/keys if you suspect your local environment has been compromised.\n\nThank you for your patience as we worked to keep the Pantheon community secure.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "none",
340
+ "last_seen": "2026-09-04T14:19:03Z",
341
  "resolved_at": "2026-04-16T13:30:53.991-07:00",
342
  "resolved_inferred": false,
343
  "started_at": "2026-04-15T07:27:54.000-07:00",
 
350
  "body": "This incident has been resolved.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "major",
353
+ "last_seen": "2026-09-04T14:19:03Z",
354
  "resolved_at": "2026-04-16T07:47:49.418-07:00",
355
  "resolved_inferred": false,
356
  "started_at": "2026-04-15T03:40:19.117-07:00",
 
363
  "body": "This incident is resolved and the Pantheon platform is operating normally. Our engineering team confirms stability across the platform. We are actively improving the system against future incidents.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "minor",
366
+ "last_seen": "2026-09-04T14:19:03Z",
367
  "resolved_at": "2026-04-03T14:46:05.016-07:00",
368
  "resolved_inferred": false,
369
  "started_at": "2026-03-30T03:22:20.415-07:00",
 
376
  "body": "This incident has been resolved.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "minor",
379
+ "last_seen": "2026-09-04T14:19:03Z",
380
  "resolved_at": "2026-03-28T07:30:33.426-07:00",
381
  "resolved_inferred": false,
382
  "started_at": "2026-03-28T05:41:54.985-07:00",
 
389
  "body": "This incident has been resolved. All Dashboard and Terminus operations are operational now.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "minor",
392
+ "last_seen": "2026-09-04T14:19:03Z",
393
  "resolved_at": "2026-03-27T16:41:31.878-07:00",
394
  "resolved_inferred": false,
395
  "started_at": "2026-03-26T05:22:53.179-07:00",
 
402
  "body": "This incident has been resolved.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "minor",
405
+ "last_seen": "2026-09-04T14:19:03Z",
406
  "resolved_at": "2026-03-17T18:43:40.634-07:00",
407
  "resolved_inferred": false,
408
  "started_at": "2026-03-11T08:49:25.655-07:00",
 
415
  "body": "This incident has been resolved.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "minor",
418
+ "last_seen": "2026-09-04T14:19:03Z",
419
  "resolved_at": "2026-03-09T07:11:53.207-07:00",
420
  "resolved_inferred": false,
421
  "started_at": "2026-03-08T17:30:22.821-07:00",
 
428
  "body": "This incident has been resolved.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "minor",
431
+ "last_seen": "2026-09-04T14:19:03Z",
432
  "resolved_at": "2026-02-22T19:05:12.180-08:00",
433
  "resolved_inferred": false,
434
  "started_at": "2026-02-22T15:57:19.068-08:00",
 
441
  "body": "This incident has been resolved.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "minor",
444
+ "last_seen": "2026-09-04T14:19:03Z",
445
  "resolved_at": "2026-02-10T14:07:43.430-08:00",
446
  "resolved_inferred": false,
447
  "started_at": "2026-02-10T13:07:26.548-08:00",
 
454
  "body": "This incident has been resolved.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "minor",
457
+ "last_seen": "2026-09-04T14:19:03Z",
458
  "resolved_at": "2026-02-09T10:56:17.885-08:00",
459
  "resolved_inferred": false,
460
  "started_at": "2026-02-09T09:31:51.082-08:00",
 
467
  "body": "This incident has been resolved, and the Dashboard has returned to normal operation.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "minor",
470
+ "last_seen": "2026-09-04T14:19:03Z",
471
  "resolved_at": "2026-02-04T11:34:04.489-08:00",
472
  "resolved_inferred": false,
473
  "started_at": "2026-02-04T10:17:51.231-08:00",
 
480
  "body": "This incident has been resolved. Thank you for your patience. Secure Integration is now working as expected.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "minor",
483
+ "last_seen": "2026-09-04T14:19:03Z",
484
  "resolved_at": "2026-01-29T16:31:46.213-08:00",
485
  "resolved_inferred": false,
486
  "started_at": "2026-01-29T15:49:41.947-08:00",
 
493
  "body": "This incident has been resolved.",
494
  "first_seen": "2026-09-04T07:06:16Z",
495
  "impact": "minor",
496
+ "last_seen": "2026-09-04T14:19:03Z",
497
  "resolved_at": "2026-01-29T17:38:32.696-08:00",
498
  "resolved_inferred": false,
499
  "started_at": "2026-01-29T09:01:25.661-08:00",
 
506
  "body": "This incident has been resolved.",
507
  "first_seen": "2026-09-04T07:06:16Z",
508
  "impact": "minor",
509
+ "last_seen": "2026-09-04T14:19:03Z",
510
  "resolved_at": "2025-12-10T00:55:04.038-08:00",
511
  "resolved_inferred": false,
512
  "started_at": "2025-12-09T22:52:59.837-08:00",
 
519
  "body": "This incident has been resolved, and the Dashboard is now functioning as expected. \n\nIf you experience any further issues, please don\u2019t hesitate to let us know through support chats or by opening a ticket.",
520
  "first_seen": "2026-09-04T07:06:16Z",
521
  "impact": "minor",
522
+ "last_seen": "2026-09-04T14:19:03Z",
523
  "resolved_at": "2025-12-09T12:52:29.539-08:00",
524
  "resolved_inferred": false,
525
  "started_at": "2025-12-09T09:48:07.574-08:00",
 
532
  "body": "This incident has been resolved.",
533
  "first_seen": "2026-09-04T07:06:16Z",
534
  "impact": "minor",
535
+ "last_seen": "2026-09-04T14:19:03Z",
536
  "resolved_at": "2025-12-02T12:24:25.773-08:00",
537
  "resolved_inferred": false,
538
  "started_at": "2025-12-02T11:08:32.865-08:00",
 
545
  "body": "This incident has been resolved.",
546
  "first_seen": "2026-09-04T07:06:16Z",
547
  "impact": "minor",
548
+ "last_seen": "2026-09-04T14:19:03Z",
549
  "resolved_at": "2025-11-18T15:11:05.335-08:00",
550
  "resolved_inferred": false,
551
  "started_at": "2025-11-18T12:09:26.067-08:00",
 
558
  "body": "This incident has been resolved.",
559
  "first_seen": "2026-09-04T07:06:16Z",
560
  "impact": "minor",
561
+ "last_seen": "2026-09-04T14:19:03Z",
562
  "resolved_at": "2025-10-28T03:33:47.990-07:00",
563
  "resolved_inferred": false,
564
  "started_at": "2025-10-27T03:13:57.108-07:00",
 
571
  "body": "This incident has been resolved. Dashboard Operations are back to normal.",
572
  "first_seen": "2026-09-04T07:06:16Z",
573
  "impact": "minor",
574
+ "last_seen": "2026-09-04T14:19:03Z",
575
  "resolved_at": "2025-10-14T23:51:48.035-07:00",
576
  "resolved_inferred": false,
577
  "started_at": "2025-10-14T21:53:10.704-07:00",
 
584
  "body": "This incident has been resolved. Dashboard operations are back to normal. Thank you for your patience throughout the process.",
585
  "first_seen": "2026-09-04T07:06:16Z",
586
  "impact": "minor",
587
+ "last_seen": "2026-09-04T14:19:03Z",
588
  "resolved_at": "2025-10-08T19:48:51.447-07:00",
589
  "resolved_inferred": false,
590
  "started_at": "2025-10-08T17:52:43.577-07:00",
 
597
  "body": "This incident has been resolved.",
598
  "first_seen": "2026-09-04T07:06:16Z",
599
  "impact": "minor",
600
+ "last_seen": "2026-09-04T14:19:03Z",
601
  "resolved_at": "2025-10-02T16:40:09.146-07:00",
602
  "resolved_inferred": false,
603
  "started_at": "2025-10-01T10:19:59.119-07:00",
 
610
  "body": "This incident has been resolved.",
611
  "first_seen": "2026-09-04T07:06:16Z",
612
  "impact": "minor",
613
+ "last_seen": "2026-09-04T14:19:03Z",
614
  "resolved_at": "2025-09-18T03:14:12.026-07:00",
615
  "resolved_inferred": false,
616
  "started_at": "2025-09-15T14:09:33.787-07:00",
 
623
  "body": "This incident has been resolved.",
624
  "first_seen": "2026-09-04T07:06:16Z",
625
  "impact": "minor",
626
+ "last_seen": "2026-09-04T14:19:03Z",
627
  "resolved_at": "2025-09-15T07:12:45.294-07:00",
628
  "resolved_inferred": false,
629
  "started_at": "2025-09-15T02:53:49.386-07:00",
 
636
  "body": "This incident has been resolved.",
637
  "first_seen": "2026-09-04T07:06:16Z",
638
  "impact": "minor",
639
+ "last_seen": "2026-09-04T14:19:03Z",
640
  "resolved_at": "2025-09-10T17:40:05.590-07:00",
641
  "resolved_inferred": false,
642
  "started_at": "2025-09-10T17:00:08.750-07:00",
 
649
  "body": "The analysis of final vendor logs produced no additional information or signs of compromise.",
650
  "first_seen": "2026-09-04T07:06:16Z",
651
  "impact": "maintenance",
652
+ "last_seen": "2026-09-04T14:19:03Z",
653
  "resolved_at": "2025-09-26T14:55:58.430-07:00",
654
  "resolved_inferred": false,
655
  "started_at": "2025-09-05T13:50:36.000-07:00",
api/v/panther-labs.json CHANGED
@@ -3,27 +3,29 @@
3
  "slug": "panther-labs",
4
  "platform": "statuspage",
5
  "status_url": "https://status.panther.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
10
  "incidents": [
11
  {
12
- "body": "Snowflake has implemented a fix and service has been restored.\n(https://status.snowflake.com/incidents/fl9tkpj8d7hk) \nWe\u2019re continuing to monitor the environment to ensure all services are functioning normally.\n\nThanks for your patience.",
13
  "first_seen": "2026-09-04T08:27:10Z",
14
  "impact": "major",
15
- "last_seen": "2026-09-04T12:24:18Z",
 
 
16
  "started_at": "2026-09-04T01:24:06.000-07:00",
17
- "state": "monitoring",
18
  "title": "Snowflake Outage Europe (Frankfurt) // eu-central-1",
19
- "updated_at": "2026-09-04T02:59:00.465-07:00",
20
  "url": "https://stspg.io/6lg7jdhqqbpp"
21
  },
22
  {
23
  "body": "This incident has been resolved.",
24
  "first_seen": "2026-09-04T07:06:16Z",
25
  "impact": "major",
26
- "last_seen": "2026-09-04T12:24:18Z",
27
  "resolved_at": "2026-08-03T23:07:13.402-07:00",
28
  "resolved_inferred": false,
29
  "started_at": "2026-08-03T08:20:20.152-07:00",
@@ -36,7 +38,7 @@
36
  "body": "Panther services have fully recovered from the regional AWS outage in us-east-1, and all systems are now operating normally.\n\nDuring the incident, some customers experienced intermittent authentication errors and delays in data ingestion, enrichment, detection processing, and alert generation. All impacted components have since stabilized, and ingestion pipelines have caught up. No further action is required from customers.",
37
  "first_seen": "2026-09-04T07:06:16Z",
38
  "impact": "minor",
39
- "last_seen": "2026-09-04T12:24:18Z",
40
  "resolved_at": "2025-10-21T10:39:45.629-07:00",
41
  "resolved_inferred": false,
42
  "started_at": "2025-10-20T11:55:36.305-07:00",
 
3
  "slug": "panther-labs",
4
  "platform": "statuspage",
5
  "status_url": "https://status.panther.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
10
  "incidents": [
11
  {
12
+ "body": "Snowflake has confirmed that the issue has been resolved and service has been restored. We\u2019ve confirmed that Panther services are operating normally and will continue to monitor the environment.",
13
  "first_seen": "2026-09-04T08:27:10Z",
14
  "impact": "major",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
+ "resolved_at": "2026-09-04T05:46:42.675-07:00",
17
+ "resolved_inferred": false,
18
  "started_at": "2026-09-04T01:24:06.000-07:00",
19
+ "state": "resolved",
20
  "title": "Snowflake Outage Europe (Frankfurt) // eu-central-1",
21
+ "updated_at": "2026-09-04T05:46:42.689-07:00",
22
  "url": "https://stspg.io/6lg7jdhqqbpp"
23
  },
24
  {
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-08-03T23:07:13.402-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-03T08:20:20.152-07:00",
 
38
  "body": "Panther services have fully recovered from the regional AWS outage in us-east-1, and all systems are now operating normally.\n\nDuring the incident, some customers experienced intermittent authentication errors and delays in data ingestion, enrichment, detection processing, and alert generation. All impacted components have since stabilized, and ingestion pipelines have caught up. No further action is required from customers.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2025-10-21T10:39:45.629-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2025-10-20T11:55:36.305-07:00",
api/v/paperspace.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "paperspace",
4
  "platform": "statuspage",
5
  "status_url": "https://status.paperspace.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "Our Engineering team has confirmed that the issue preventing users from accessing or logging in to the Paperspace Console has been resolved, and the service has been fully restored.\n\nThank you for your patience and understanding throughout this incident. If you continue to experience any issues, please reach out to our Support team, and we will be happy to assist you further.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "critical",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-08-26T07:50:05.862-04:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-26T06:46:19.938-04:00",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved now.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-05-26T01:04:29.406-04:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-05-25T21:30:05.000-04:00",
@@ -38,7 +38,7 @@
38
  "body": "Our Engineering team has resolved the incident with intermittent connectivity issues affecting a few Core VMs in the NY2 data center. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-05-08T18:02:50.076-04:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-05-08T14:08:35.016-04:00",
@@ -51,7 +51,7 @@
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-04-20T13:32:40.092-04:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-04-20T11:32:08.626-04:00",
@@ -64,7 +64,7 @@
64
  "body": "The issue affecting a subset of GPU instances in the NYC region has been resolved. Customers using P5000, P6000, and RTX5000 instances may have previously experienced difficulties when attempting to power on these resources.\n\nImportantly, this issue had no impact on running instances, only power-on actions were affected.\n\nOur engineering team has implemented a fix and is continuing to monitor the environment to ensure stability.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "major",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-04-18T13:19:10.863-04:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-04-18T11:00:50.217-04:00",
@@ -77,7 +77,7 @@
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-01-16T11:21:28.401-05:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-01-16T05:27:25.078-05:00",
@@ -90,7 +90,7 @@
90
  "body": "This incident has been resolved. The core VMs should be working as intended. Thanks for your cooperation.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "major",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-01-16T07:48:57.371-05:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-01-16T05:09:31.030-05:00",
@@ -103,7 +103,7 @@
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "major",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-01-16T11:21:47.612-05:00",
108
  "resolved_inferred": false,
109
  "started_at": "2025-12-26T09:55:48.839-05:00",
@@ -116,7 +116,7 @@
116
  "body": "This incident has been resolved. The core machines should be working as intended. Thank you for your patience and cooperation.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "critical",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2025-12-10T03:05:29.499-05:00",
121
  "resolved_inferred": false,
122
  "started_at": "2025-12-10T01:00:43.149-05:00",
@@ -129,7 +129,7 @@
129
  "body": "This incident has been resolved. Thank you everyone.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "none",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2025-12-05T05:19:55.675-05:00",
134
  "resolved_inferred": false,
135
  "started_at": "2025-12-05T04:23:41.721-05:00",
@@ -142,7 +142,7 @@
142
  "body": "The incident in the AMS region has been fully resolved, and all services are now available. If you experience any further issues, please don't hesitate to contact our support team for assistance.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "critical",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2025-12-01T21:30:15.973-05:00",
147
  "resolved_inferred": false,
148
  "started_at": "2025-11-30T19:04:06.258-05:00",
@@ -155,7 +155,7 @@
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "major",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2025-10-23T23:54:49.636-04:00",
160
  "resolved_inferred": false,
161
  "started_at": "2025-10-23T22:06:35.759-04:00",
@@ -168,7 +168,7 @@
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2025-10-04T19:40:52.000-04:00",
173
  "resolved_inferred": false,
174
  "started_at": "2025-10-03T04:44:17.000-04:00",
@@ -181,7 +181,7 @@
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "minor",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2025-08-28T11:53:13.902-04:00",
186
  "resolved_inferred": false,
187
  "started_at": "2025-08-28T08:46:29.740-04:00",
 
3
  "slug": "paperspace",
4
  "platform": "statuspage",
5
  "status_url": "https://status.paperspace.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "Our Engineering team has confirmed that the issue preventing users from accessing or logging in to the Paperspace Console has been resolved, and the service has been fully restored.\n\nThank you for your patience and understanding throughout this incident. If you continue to experience any issues, please reach out to our Support team, and we will be happy to assist you further.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "critical",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-08-26T07:50:05.862-04:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-26T06:46:19.938-04:00",
 
25
  "body": "This incident has been resolved now.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-05-26T01:04:29.406-04:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-05-25T21:30:05.000-04:00",
 
38
  "body": "Our Engineering team has resolved the incident with intermittent connectivity issues affecting a few Core VMs in the NY2 data center. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-05-08T18:02:50.076-04:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-05-08T14:08:35.016-04:00",
 
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-04-20T13:32:40.092-04:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-04-20T11:32:08.626-04:00",
 
64
  "body": "The issue affecting a subset of GPU instances in the NYC region has been resolved. Customers using P5000, P6000, and RTX5000 instances may have previously experienced difficulties when attempting to power on these resources.\n\nImportantly, this issue had no impact on running instances, only power-on actions were affected.\n\nOur engineering team has implemented a fix and is continuing to monitor the environment to ensure stability.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "major",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-04-18T13:19:10.863-04:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-04-18T11:00:50.217-04:00",
 
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-01-16T11:21:28.401-05:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-01-16T05:27:25.078-05:00",
 
90
  "body": "This incident has been resolved. The core VMs should be working as intended. Thanks for your cooperation.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "major",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-01-16T07:48:57.371-05:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-01-16T05:09:31.030-05:00",
 
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "major",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-01-16T11:21:47.612-05:00",
108
  "resolved_inferred": false,
109
  "started_at": "2025-12-26T09:55:48.839-05:00",
 
116
  "body": "This incident has been resolved. The core machines should be working as intended. Thank you for your patience and cooperation.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "critical",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2025-12-10T03:05:29.499-05:00",
121
  "resolved_inferred": false,
122
  "started_at": "2025-12-10T01:00:43.149-05:00",
 
129
  "body": "This incident has been resolved. Thank you everyone.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "none",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2025-12-05T05:19:55.675-05:00",
134
  "resolved_inferred": false,
135
  "started_at": "2025-12-05T04:23:41.721-05:00",
 
142
  "body": "The incident in the AMS region has been fully resolved, and all services are now available. If you experience any further issues, please don't hesitate to contact our support team for assistance.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "critical",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2025-12-01T21:30:15.973-05:00",
147
  "resolved_inferred": false,
148
  "started_at": "2025-11-30T19:04:06.258-05:00",
 
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "major",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2025-10-23T23:54:49.636-04:00",
160
  "resolved_inferred": false,
161
  "started_at": "2025-10-23T22:06:35.759-04:00",
 
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2025-10-04T19:40:52.000-04:00",
173
  "resolved_inferred": false,
174
  "started_at": "2025-10-03T04:44:17.000-04:00",
 
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "minor",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2025-08-28T11:53:13.902-04:00",
186
  "resolved_inferred": false,
187
  "started_at": "2025-08-28T08:46:29.740-04:00",
api/v/parchment.json CHANGED
@@ -3,27 +3,38 @@
3
  "slug": "parchment",
4
  "platform": "statuspage",
5
  "status_url": "https://status.parchment.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
- "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
10
  "incidents": [
11
  {
 
 
 
 
 
 
 
 
 
 
 
12
  "body": "Weather in Manila kept about a third of our support team out today, so we're shortening live support hours to 10 am\u20134 pm, ET, starting today through the end of the week. That applies to phones and to live chat: within those hours chat transfers to a human agent, and outside them it doesn't.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
- "impact": "none",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "started_at": "2026-08-17T16:59:03.121Z",
17
  "state": "investigating",
18
  "title": "Limited Consumer Support Hours",
19
- "updated_at": "2026-08-17T16:59:03.176Z",
20
  "url": "https://stspg.io/5flg0988nvmj"
21
  },
22
  {
23
  "body": "This incident has been resolved.",
24
  "first_seen": "2026-09-04T07:06:16Z",
25
  "impact": "none",
26
- "last_seen": "2026-09-04T12:24:18Z",
27
  "resolved_at": "2026-07-30T21:47:59.387Z",
28
  "resolved_inferred": false,
29
  "started_at": "2026-07-30T20:17:24.802Z",
@@ -36,7 +47,7 @@
36
  "body": "This incident has been resolved.",
37
  "first_seen": "2026-09-04T07:06:16Z",
38
  "impact": "minor",
39
- "last_seen": "2026-09-04T12:24:18Z",
40
  "resolved_at": "2026-07-27T20:37:15.715Z",
41
  "resolved_inferred": false,
42
  "started_at": "2026-07-27T14:41:17.732Z",
@@ -49,7 +60,7 @@
49
  "body": "This incident has been resolved.",
50
  "first_seen": "2026-09-04T07:06:16Z",
51
  "impact": "minor",
52
- "last_seen": "2026-09-04T12:24:18Z",
53
  "resolved_at": "2026-07-20T23:03:38.194Z",
54
  "resolved_inferred": false,
55
  "started_at": "2026-07-20T21:12:27.700Z",
@@ -62,7 +73,7 @@
62
  "body": "This incident has been resolved.",
63
  "first_seen": "2026-09-04T07:06:16Z",
64
  "impact": "maintenance",
65
- "last_seen": "2026-09-04T12:24:18Z",
66
  "resolved_at": "2026-06-28T03:05:28.806Z",
67
  "resolved_inferred": false,
68
  "started_at": "2026-06-27T19:01:12.521Z",
@@ -75,7 +86,7 @@
75
  "body": "This incident has been resolved.",
76
  "first_seen": "2026-09-04T07:06:16Z",
77
  "impact": "none",
78
- "last_seen": "2026-09-04T12:24:18Z",
79
  "resolved_at": "2026-06-22T13:38:37.367Z",
80
  "resolved_inferred": false,
81
  "started_at": "2026-06-18T23:00:11.709Z",
@@ -88,7 +99,7 @@
88
  "body": "This incident has been resolved. All impacted orders have been successfully sent.",
89
  "first_seen": "2026-09-04T07:06:16Z",
90
  "impact": "minor",
91
- "last_seen": "2026-09-04T12:24:18Z",
92
  "resolved_at": "2026-06-05T23:03:22.704Z",
93
  "resolved_inferred": false,
94
  "started_at": "2026-06-05T18:50:49.000Z",
@@ -101,7 +112,7 @@
101
  "body": "This incident has been resolved.",
102
  "first_seen": "2026-09-04T07:06:16Z",
103
  "impact": "none",
104
- "last_seen": "2026-09-04T12:24:18Z",
105
  "resolved_at": "2026-06-04T17:30:44.671Z",
106
  "resolved_inferred": false,
107
  "started_at": "2026-06-04T16:18:15.620Z",
@@ -114,7 +125,7 @@
114
  "body": "This incident has been resolved.",
115
  "first_seen": "2026-09-04T07:06:16Z",
116
  "impact": "major",
117
- "last_seen": "2026-09-04T12:24:18Z",
118
  "resolved_at": "2026-05-27T21:43:32.193Z",
119
  "resolved_inferred": false,
120
  "started_at": "2026-05-19T16:36:06.789Z",
@@ -127,7 +138,7 @@
127
  "body": "This incident has been resolved.",
128
  "first_seen": "2026-09-04T07:06:16Z",
129
  "impact": "major",
130
- "last_seen": "2026-09-04T12:24:18Z",
131
  "resolved_at": "2026-05-27T21:43:43.072Z",
132
  "resolved_inferred": false,
133
  "started_at": "2026-05-18T17:46:10.365Z",
@@ -140,7 +151,7 @@
140
  "body": "This incident has been resolved and we will continue to monitor login times.",
141
  "first_seen": "2026-09-04T07:06:16Z",
142
  "impact": "maintenance",
143
- "last_seen": "2026-09-04T12:24:18Z",
144
  "resolved_at": "2026-05-11T19:16:15.876Z",
145
  "resolved_inferred": false,
146
  "started_at": "2026-05-11T16:40:13.219Z",
@@ -153,7 +164,7 @@
153
  "body": "All Canvas environments are available.",
154
  "first_seen": "2026-09-04T07:06:16Z",
155
  "impact": "maintenance",
156
- "last_seen": "2026-09-04T12:24:18Z",
157
  "resolved_at": "2026-05-11T22:35:11.156Z",
158
  "resolved_inferred": false,
159
  "started_at": "2026-05-07T22:36:18.837Z",
@@ -166,7 +177,7 @@
166
  "body": "ParchieBot is now live.\nUsers can now visit parchment.com/chat-support to search help center articles, chat with an agent, or get answers from Parchie bot directly. This gives learners a faster way to find help without waiting in a queue.",
167
  "first_seen": "2026-09-04T07:06:16Z",
168
  "impact": "minor",
169
- "last_seen": "2026-09-04T12:24:18Z",
170
  "resolved_at": "2026-06-16T14:48:35.674Z",
171
  "resolved_inferred": false,
172
  "started_at": "2026-05-05T17:21:38.871Z",
@@ -179,7 +190,7 @@
179
  "body": "This incident has been resolved.",
180
  "first_seen": "2026-09-04T07:06:16Z",
181
  "impact": "minor",
182
- "last_seen": "2026-09-04T12:24:18Z",
183
  "resolved_at": "2026-05-06T22:16:28.138Z",
184
  "resolved_inferred": false,
185
  "started_at": "2026-05-05T16:41:38.382Z",
@@ -192,7 +203,7 @@
192
  "body": "A fix has been implemented and all formats of phone numbers are accepted.",
193
  "first_seen": "2026-09-04T07:06:16Z",
194
  "impact": "minor",
195
- "last_seen": "2026-09-04T12:24:18Z",
196
  "resolved_at": "2026-05-06T15:04:32.066Z",
197
  "resolved_inferred": false,
198
  "started_at": "2026-05-05T15:43:46.150Z",
@@ -205,7 +216,7 @@
205
  "body": "This incident is resolved.",
206
  "first_seen": "2026-09-04T07:06:16Z",
207
  "impact": "minor",
208
- "last_seen": "2026-09-04T12:24:18Z",
209
  "resolved_at": "2026-05-01T18:35:55.261Z",
210
  "resolved_inferred": false,
211
  "started_at": "2026-05-01T16:09:12.588Z",
@@ -218,7 +229,7 @@
218
  "body": "This incident has been resolved.",
219
  "first_seen": "2026-09-04T07:06:16Z",
220
  "impact": "major",
221
- "last_seen": "2026-09-04T12:24:18Z",
222
  "resolved_at": "2026-03-31T21:25:02.218Z",
223
  "resolved_inferred": false,
224
  "started_at": "2026-03-31T18:23:56.530Z",
@@ -231,7 +242,7 @@
231
  "body": "This incident has been resolved.",
232
  "first_seen": "2026-09-04T07:06:16Z",
233
  "impact": "major",
234
- "last_seen": "2026-09-04T12:24:18Z",
235
  "resolved_at": "2026-03-30T21:39:13.538Z",
236
  "resolved_inferred": false,
237
  "started_at": "2026-03-30T16:50:23.929Z",
@@ -244,7 +255,7 @@
244
  "body": "This incident has been resolved.",
245
  "first_seen": "2026-09-04T07:06:16Z",
246
  "impact": "minor",
247
- "last_seen": "2026-09-04T12:24:18Z",
248
  "resolved_at": "2026-03-30T14:50:15.258Z",
249
  "resolved_inferred": false,
250
  "started_at": "2026-03-30T14:23:45.469Z",
@@ -257,7 +268,7 @@
257
  "body": "Maintenance has been completed.",
258
  "first_seen": "2026-09-04T07:06:16Z",
259
  "impact": "none",
260
- "last_seen": "2026-09-04T12:24:18Z",
261
  "resolved_at": "2026-03-28T19:17:29.803Z",
262
  "resolved_inferred": false,
263
  "started_at": "2026-03-28T16:02:51.226Z",
@@ -270,7 +281,7 @@
270
  "body": "This incident has been resolved.",
271
  "first_seen": "2026-09-04T07:06:16Z",
272
  "impact": "minor",
273
- "last_seen": "2026-09-04T12:24:18Z",
274
  "resolved_at": "2026-03-16T20:20:33.815Z",
275
  "resolved_inferred": false,
276
  "started_at": "2026-03-16T18:21:18.950Z",
@@ -283,7 +294,7 @@
283
  "body": "This incident has been resolved.",
284
  "first_seen": "2026-09-04T07:06:16Z",
285
  "impact": "minor",
286
- "last_seen": "2026-09-04T12:24:18Z",
287
  "resolved_at": "2026-03-13T22:08:45.441Z",
288
  "resolved_inferred": false,
289
  "started_at": "2026-03-13T13:36:04.016Z",
@@ -296,7 +307,7 @@
296
  "body": "This incident has been resolved.",
297
  "first_seen": "2026-09-04T07:06:16Z",
298
  "impact": "none",
299
- "last_seen": "2026-09-04T12:24:18Z",
300
  "resolved_at": "2026-03-11T20:18:52.635Z",
301
  "resolved_inferred": false,
302
  "started_at": "2026-03-11T16:54:34.598Z",
@@ -309,7 +320,7 @@
309
  "body": "This incident has been resolved.",
310
  "first_seen": "2026-09-04T07:06:16Z",
311
  "impact": "minor",
312
- "last_seen": "2026-09-04T12:24:18Z",
313
  "resolved_at": "2026-02-27T22:15:41.779Z",
314
  "resolved_inferred": false,
315
  "started_at": "2026-02-27T20:18:17.829Z",
@@ -322,7 +333,7 @@
322
  "body": "1/27/2026 - The Parchment Print Operations have resumed normal activities.",
323
  "first_seen": "2026-09-04T07:06:16Z",
324
  "impact": "major",
325
- "last_seen": "2026-09-04T12:24:18Z",
326
  "resolved_at": "2026-01-27T14:34:01.000Z",
327
  "resolved_inferred": false,
328
  "started_at": "2026-01-26T14:01:04.202Z",
@@ -335,7 +346,7 @@
335
  "body": "This incident has been resolved.",
336
  "first_seen": "2026-09-04T07:06:16Z",
337
  "impact": "none",
338
- "last_seen": "2026-09-04T12:24:18Z",
339
  "resolved_at": "2025-12-15T19:16:21.698Z",
340
  "resolved_inferred": false,
341
  "started_at": "2025-12-15T18:20:01.908Z",
@@ -348,7 +359,7 @@
348
  "body": "All backlogged orders have been processed and new orders are being fulfilled as expected.",
349
  "first_seen": "2026-09-04T07:06:16Z",
350
  "impact": "major",
351
- "last_seen": "2026-09-04T12:24:18Z",
352
  "resolved_at": "2025-12-01T21:25:26.426Z",
353
  "resolved_inferred": false,
354
  "started_at": "2025-12-01T16:56:42.263Z",
@@ -361,7 +372,7 @@
361
  "body": "This incident has been resolved.",
362
  "first_seen": "2026-09-04T07:06:16Z",
363
  "impact": "none",
364
- "last_seen": "2026-09-04T12:24:18Z",
365
  "resolved_at": "2025-11-22T05:28:02.948Z",
366
  "resolved_inferred": false,
367
  "started_at": "2025-11-21T15:52:42.638Z",
@@ -374,7 +385,7 @@
374
  "body": "We are investigating an issue where traffic routed to parchment.com without www is inconsistently redirecting. However, traffic to www.parchment.com should continue to function as expected. We will post more info as it becomes available.",
375
  "first_seen": "2026-09-04T07:06:16Z",
376
  "impact": "minor",
377
- "last_seen": "2026-09-04T12:24:18Z",
378
  "resolved_at": "2025-11-21T14:28:47.000Z",
379
  "resolved_inferred": false,
380
  "started_at": "2025-11-21T14:28:47.000Z",
@@ -387,7 +398,7 @@
387
  "body": "This incident has been resolved.",
388
  "first_seen": "2026-09-04T07:06:16Z",
389
  "impact": "none",
390
- "last_seen": "2026-09-04T12:24:18Z",
391
  "resolved_at": "2025-12-01T19:15:57.945Z",
392
  "resolved_inferred": false,
393
  "started_at": "2025-11-19T15:57:03.721Z",
@@ -400,7 +411,7 @@
400
  "body": "This incident has been resolved.",
401
  "first_seen": "2026-09-04T07:06:16Z",
402
  "impact": "major",
403
- "last_seen": "2026-09-04T12:24:18Z",
404
  "resolved_at": "2025-11-18T15:35:39.725Z",
405
  "resolved_inferred": false,
406
  "started_at": "2025-11-18T13:46:29.503Z",
@@ -413,7 +424,7 @@
413
  "body": "This incident has been resolved.",
414
  "first_seen": "2026-09-04T07:06:16Z",
415
  "impact": "minor",
416
- "last_seen": "2026-09-04T12:24:18Z",
417
  "resolved_at": "2025-11-10T20:46:36.771Z",
418
  "resolved_inferred": false,
419
  "started_at": "2025-11-10T14:13:38.603Z",
@@ -426,7 +437,7 @@
426
  "body": "After monitoring an applied fix, performance has been stable for the past several hours. Order processing is operating nominally.",
427
  "first_seen": "2026-09-04T07:06:16Z",
428
  "impact": "minor",
429
- "last_seen": "2026-09-04T12:24:18Z",
430
  "resolved_at": "2025-10-27T19:22:12.440Z",
431
  "resolved_inferred": false,
432
  "started_at": "2025-10-27T14:29:13.482Z",
@@ -439,7 +450,7 @@
439
  "body": "This incident has been resolved.",
440
  "first_seen": "2026-09-04T07:06:16Z",
441
  "impact": "none",
442
- "last_seen": "2026-09-04T12:24:18Z",
443
  "resolved_at": "2025-10-23T13:31:28.743Z",
444
  "resolved_inferred": false,
445
  "started_at": "2025-10-22T20:15:20.581Z",
@@ -452,7 +463,7 @@
452
  "body": "Over the weekend of monitoring, resolution for this incident has remained stable. This incident is resolved.",
453
  "first_seen": "2026-09-04T07:06:16Z",
454
  "impact": "minor",
455
- "last_seen": "2026-09-04T12:24:18Z",
456
  "resolved_at": "2025-10-27T14:26:53.919Z",
457
  "resolved_inferred": false,
458
  "started_at": "2025-10-22T13:38:56.235Z",
@@ -465,7 +476,7 @@
465
  "body": "This incident has been resolved.",
466
  "first_seen": "2026-09-04T07:06:16Z",
467
  "impact": "minor",
468
- "last_seen": "2026-09-04T12:24:18Z",
469
  "resolved_at": "2025-11-19T15:51:45.693Z",
470
  "resolved_inferred": false,
471
  "started_at": "2025-09-26T14:05:32.538Z",
@@ -478,7 +489,7 @@
478
  "body": "This incident has been resolved.",
479
  "first_seen": "2026-09-04T07:06:16Z",
480
  "impact": "major",
481
- "last_seen": "2026-09-04T12:24:18Z",
482
  "resolved_at": "2025-09-26T20:02:34.263Z",
483
  "resolved_inferred": false,
484
  "started_at": "2025-09-23T19:27:04.877Z",
@@ -491,7 +502,7 @@
491
  "body": "This incident has been resolved.",
492
  "first_seen": "2026-09-04T07:06:16Z",
493
  "impact": "none",
494
- "last_seen": "2026-09-04T12:24:18Z",
495
  "resolved_at": "2025-09-22T16:13:16.910Z",
496
  "resolved_inferred": false,
497
  "started_at": "2025-09-22T13:02:51.228Z",
@@ -504,7 +515,7 @@
504
  "body": "This incident has been resolved.",
505
  "first_seen": "2026-09-04T07:06:16Z",
506
  "impact": "minor",
507
- "last_seen": "2026-09-04T12:24:18Z",
508
  "resolved_at": "2025-09-09T20:00:13.314Z",
509
  "resolved_inferred": false,
510
  "started_at": "2025-09-09T13:45:41.298Z",
@@ -517,7 +528,7 @@
517
  "body": "This incident has been resolved.",
518
  "first_seen": "2026-09-04T07:06:16Z",
519
  "impact": "minor",
520
- "last_seen": "2026-09-04T12:24:18Z",
521
  "resolved_at": "2025-08-26T12:18:19.458Z",
522
  "resolved_inferred": false,
523
  "started_at": "2025-08-25T14:48:39.203Z",
@@ -530,7 +541,7 @@
530
  "body": "This incident has been resolved.",
531
  "first_seen": "2026-09-04T07:06:16Z",
532
  "impact": "none",
533
- "last_seen": "2026-09-04T12:24:18Z",
534
  "resolved_at": "2025-08-19T16:22:20.005Z",
535
  "resolved_inferred": false,
536
  "started_at": "2025-08-19T16:06:00.582Z",
 
3
  "slug": "parchment",
4
  "platform": "statuspage",
5
  "status_url": "https://status.parchment.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
+ "last_state": "degraded",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
10
  "incidents": [
11
  {
12
+ "body": "The issue has been identified and a fix is being implemented from the service provider. We will provide another update as soon as it becomes available.",
13
+ "first_seen": "2026-09-04T14:19:03Z",
14
+ "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
+ "started_at": "2026-09-04T12:39:55.468Z",
17
+ "state": "identified",
18
+ "title": "MFA code emails not being sent",
19
+ "updated_at": "2026-09-04T13:36:59.030Z",
20
+ "url": "https://stspg.io/t3078gy7stgy"
21
+ },
22
+ {
23
  "body": "Weather in Manila kept about a third of our support team out today, so we're shortening live support hours to 10 am\u20134 pm, ET, starting today through the end of the week. That applies to phones and to live chat: within those hours chat transfers to a human agent, and outside them it doesn't.",
24
  "first_seen": "2026-09-04T07:06:16Z",
25
+ "impact": "minor",
26
+ "last_seen": "2026-09-04T14:19:03Z",
27
  "started_at": "2026-08-17T16:59:03.121Z",
28
  "state": "investigating",
29
  "title": "Limited Consumer Support Hours",
30
+ "updated_at": "2026-09-04T12:39:55.540Z",
31
  "url": "https://stspg.io/5flg0988nvmj"
32
  },
33
  {
34
  "body": "This incident has been resolved.",
35
  "first_seen": "2026-09-04T07:06:16Z",
36
  "impact": "none",
37
+ "last_seen": "2026-09-04T14:19:03Z",
38
  "resolved_at": "2026-07-30T21:47:59.387Z",
39
  "resolved_inferred": false,
40
  "started_at": "2026-07-30T20:17:24.802Z",
 
47
  "body": "This incident has been resolved.",
48
  "first_seen": "2026-09-04T07:06:16Z",
49
  "impact": "minor",
50
+ "last_seen": "2026-09-04T14:19:03Z",
51
  "resolved_at": "2026-07-27T20:37:15.715Z",
52
  "resolved_inferred": false,
53
  "started_at": "2026-07-27T14:41:17.732Z",
 
60
  "body": "This incident has been resolved.",
61
  "first_seen": "2026-09-04T07:06:16Z",
62
  "impact": "minor",
63
+ "last_seen": "2026-09-04T14:19:03Z",
64
  "resolved_at": "2026-07-20T23:03:38.194Z",
65
  "resolved_inferred": false,
66
  "started_at": "2026-07-20T21:12:27.700Z",
 
73
  "body": "This incident has been resolved.",
74
  "first_seen": "2026-09-04T07:06:16Z",
75
  "impact": "maintenance",
76
+ "last_seen": "2026-09-04T14:19:03Z",
77
  "resolved_at": "2026-06-28T03:05:28.806Z",
78
  "resolved_inferred": false,
79
  "started_at": "2026-06-27T19:01:12.521Z",
 
86
  "body": "This incident has been resolved.",
87
  "first_seen": "2026-09-04T07:06:16Z",
88
  "impact": "none",
89
+ "last_seen": "2026-09-04T14:19:03Z",
90
  "resolved_at": "2026-06-22T13:38:37.367Z",
91
  "resolved_inferred": false,
92
  "started_at": "2026-06-18T23:00:11.709Z",
 
99
  "body": "This incident has been resolved. All impacted orders have been successfully sent.",
100
  "first_seen": "2026-09-04T07:06:16Z",
101
  "impact": "minor",
102
+ "last_seen": "2026-09-04T14:19:03Z",
103
  "resolved_at": "2026-06-05T23:03:22.704Z",
104
  "resolved_inferred": false,
105
  "started_at": "2026-06-05T18:50:49.000Z",
 
112
  "body": "This incident has been resolved.",
113
  "first_seen": "2026-09-04T07:06:16Z",
114
  "impact": "none",
115
+ "last_seen": "2026-09-04T14:19:03Z",
116
  "resolved_at": "2026-06-04T17:30:44.671Z",
117
  "resolved_inferred": false,
118
  "started_at": "2026-06-04T16:18:15.620Z",
 
125
  "body": "This incident has been resolved.",
126
  "first_seen": "2026-09-04T07:06:16Z",
127
  "impact": "major",
128
+ "last_seen": "2026-09-04T14:19:03Z",
129
  "resolved_at": "2026-05-27T21:43:32.193Z",
130
  "resolved_inferred": false,
131
  "started_at": "2026-05-19T16:36:06.789Z",
 
138
  "body": "This incident has been resolved.",
139
  "first_seen": "2026-09-04T07:06:16Z",
140
  "impact": "major",
141
+ "last_seen": "2026-09-04T14:19:03Z",
142
  "resolved_at": "2026-05-27T21:43:43.072Z",
143
  "resolved_inferred": false,
144
  "started_at": "2026-05-18T17:46:10.365Z",
 
151
  "body": "This incident has been resolved and we will continue to monitor login times.",
152
  "first_seen": "2026-09-04T07:06:16Z",
153
  "impact": "maintenance",
154
+ "last_seen": "2026-09-04T14:19:03Z",
155
  "resolved_at": "2026-05-11T19:16:15.876Z",
156
  "resolved_inferred": false,
157
  "started_at": "2026-05-11T16:40:13.219Z",
 
164
  "body": "All Canvas environments are available.",
165
  "first_seen": "2026-09-04T07:06:16Z",
166
  "impact": "maintenance",
167
+ "last_seen": "2026-09-04T14:19:03Z",
168
  "resolved_at": "2026-05-11T22:35:11.156Z",
169
  "resolved_inferred": false,
170
  "started_at": "2026-05-07T22:36:18.837Z",
 
177
  "body": "ParchieBot is now live.\nUsers can now visit parchment.com/chat-support to search help center articles, chat with an agent, or get answers from Parchie bot directly. This gives learners a faster way to find help without waiting in a queue.",
178
  "first_seen": "2026-09-04T07:06:16Z",
179
  "impact": "minor",
180
+ "last_seen": "2026-09-04T14:19:03Z",
181
  "resolved_at": "2026-06-16T14:48:35.674Z",
182
  "resolved_inferred": false,
183
  "started_at": "2026-05-05T17:21:38.871Z",
 
190
  "body": "This incident has been resolved.",
191
  "first_seen": "2026-09-04T07:06:16Z",
192
  "impact": "minor",
193
+ "last_seen": "2026-09-04T14:19:03Z",
194
  "resolved_at": "2026-05-06T22:16:28.138Z",
195
  "resolved_inferred": false,
196
  "started_at": "2026-05-05T16:41:38.382Z",
 
203
  "body": "A fix has been implemented and all formats of phone numbers are accepted.",
204
  "first_seen": "2026-09-04T07:06:16Z",
205
  "impact": "minor",
206
+ "last_seen": "2026-09-04T14:19:03Z",
207
  "resolved_at": "2026-05-06T15:04:32.066Z",
208
  "resolved_inferred": false,
209
  "started_at": "2026-05-05T15:43:46.150Z",
 
216
  "body": "This incident is resolved.",
217
  "first_seen": "2026-09-04T07:06:16Z",
218
  "impact": "minor",
219
+ "last_seen": "2026-09-04T14:19:03Z",
220
  "resolved_at": "2026-05-01T18:35:55.261Z",
221
  "resolved_inferred": false,
222
  "started_at": "2026-05-01T16:09:12.588Z",
 
229
  "body": "This incident has been resolved.",
230
  "first_seen": "2026-09-04T07:06:16Z",
231
  "impact": "major",
232
+ "last_seen": "2026-09-04T14:19:03Z",
233
  "resolved_at": "2026-03-31T21:25:02.218Z",
234
  "resolved_inferred": false,
235
  "started_at": "2026-03-31T18:23:56.530Z",
 
242
  "body": "This incident has been resolved.",
243
  "first_seen": "2026-09-04T07:06:16Z",
244
  "impact": "major",
245
+ "last_seen": "2026-09-04T14:19:03Z",
246
  "resolved_at": "2026-03-30T21:39:13.538Z",
247
  "resolved_inferred": false,
248
  "started_at": "2026-03-30T16:50:23.929Z",
 
255
  "body": "This incident has been resolved.",
256
  "first_seen": "2026-09-04T07:06:16Z",
257
  "impact": "minor",
258
+ "last_seen": "2026-09-04T14:19:03Z",
259
  "resolved_at": "2026-03-30T14:50:15.258Z",
260
  "resolved_inferred": false,
261
  "started_at": "2026-03-30T14:23:45.469Z",
 
268
  "body": "Maintenance has been completed.",
269
  "first_seen": "2026-09-04T07:06:16Z",
270
  "impact": "none",
271
+ "last_seen": "2026-09-04T14:19:03Z",
272
  "resolved_at": "2026-03-28T19:17:29.803Z",
273
  "resolved_inferred": false,
274
  "started_at": "2026-03-28T16:02:51.226Z",
 
281
  "body": "This incident has been resolved.",
282
  "first_seen": "2026-09-04T07:06:16Z",
283
  "impact": "minor",
284
+ "last_seen": "2026-09-04T14:19:03Z",
285
  "resolved_at": "2026-03-16T20:20:33.815Z",
286
  "resolved_inferred": false,
287
  "started_at": "2026-03-16T18:21:18.950Z",
 
294
  "body": "This incident has been resolved.",
295
  "first_seen": "2026-09-04T07:06:16Z",
296
  "impact": "minor",
297
+ "last_seen": "2026-09-04T14:19:03Z",
298
  "resolved_at": "2026-03-13T22:08:45.441Z",
299
  "resolved_inferred": false,
300
  "started_at": "2026-03-13T13:36:04.016Z",
 
307
  "body": "This incident has been resolved.",
308
  "first_seen": "2026-09-04T07:06:16Z",
309
  "impact": "none",
310
+ "last_seen": "2026-09-04T14:19:03Z",
311
  "resolved_at": "2026-03-11T20:18:52.635Z",
312
  "resolved_inferred": false,
313
  "started_at": "2026-03-11T16:54:34.598Z",
 
320
  "body": "This incident has been resolved.",
321
  "first_seen": "2026-09-04T07:06:16Z",
322
  "impact": "minor",
323
+ "last_seen": "2026-09-04T14:19:03Z",
324
  "resolved_at": "2026-02-27T22:15:41.779Z",
325
  "resolved_inferred": false,
326
  "started_at": "2026-02-27T20:18:17.829Z",
 
333
  "body": "1/27/2026 - The Parchment Print Operations have resumed normal activities.",
334
  "first_seen": "2026-09-04T07:06:16Z",
335
  "impact": "major",
336
+ "last_seen": "2026-09-04T14:19:03Z",
337
  "resolved_at": "2026-01-27T14:34:01.000Z",
338
  "resolved_inferred": false,
339
  "started_at": "2026-01-26T14:01:04.202Z",
 
346
  "body": "This incident has been resolved.",
347
  "first_seen": "2026-09-04T07:06:16Z",
348
  "impact": "none",
349
+ "last_seen": "2026-09-04T14:19:03Z",
350
  "resolved_at": "2025-12-15T19:16:21.698Z",
351
  "resolved_inferred": false,
352
  "started_at": "2025-12-15T18:20:01.908Z",
 
359
  "body": "All backlogged orders have been processed and new orders are being fulfilled as expected.",
360
  "first_seen": "2026-09-04T07:06:16Z",
361
  "impact": "major",
362
+ "last_seen": "2026-09-04T14:19:03Z",
363
  "resolved_at": "2025-12-01T21:25:26.426Z",
364
  "resolved_inferred": false,
365
  "started_at": "2025-12-01T16:56:42.263Z",
 
372
  "body": "This incident has been resolved.",
373
  "first_seen": "2026-09-04T07:06:16Z",
374
  "impact": "none",
375
+ "last_seen": "2026-09-04T14:19:03Z",
376
  "resolved_at": "2025-11-22T05:28:02.948Z",
377
  "resolved_inferred": false,
378
  "started_at": "2025-11-21T15:52:42.638Z",
 
385
  "body": "We are investigating an issue where traffic routed to parchment.com without www is inconsistently redirecting. However, traffic to www.parchment.com should continue to function as expected. We will post more info as it becomes available.",
386
  "first_seen": "2026-09-04T07:06:16Z",
387
  "impact": "minor",
388
+ "last_seen": "2026-09-04T14:19:03Z",
389
  "resolved_at": "2025-11-21T14:28:47.000Z",
390
  "resolved_inferred": false,
391
  "started_at": "2025-11-21T14:28:47.000Z",
 
398
  "body": "This incident has been resolved.",
399
  "first_seen": "2026-09-04T07:06:16Z",
400
  "impact": "none",
401
+ "last_seen": "2026-09-04T14:19:03Z",
402
  "resolved_at": "2025-12-01T19:15:57.945Z",
403
  "resolved_inferred": false,
404
  "started_at": "2025-11-19T15:57:03.721Z",
 
411
  "body": "This incident has been resolved.",
412
  "first_seen": "2026-09-04T07:06:16Z",
413
  "impact": "major",
414
+ "last_seen": "2026-09-04T14:19:03Z",
415
  "resolved_at": "2025-11-18T15:35:39.725Z",
416
  "resolved_inferred": false,
417
  "started_at": "2025-11-18T13:46:29.503Z",
 
424
  "body": "This incident has been resolved.",
425
  "first_seen": "2026-09-04T07:06:16Z",
426
  "impact": "minor",
427
+ "last_seen": "2026-09-04T14:19:03Z",
428
  "resolved_at": "2025-11-10T20:46:36.771Z",
429
  "resolved_inferred": false,
430
  "started_at": "2025-11-10T14:13:38.603Z",
 
437
  "body": "After monitoring an applied fix, performance has been stable for the past several hours. Order processing is operating nominally.",
438
  "first_seen": "2026-09-04T07:06:16Z",
439
  "impact": "minor",
440
+ "last_seen": "2026-09-04T14:19:03Z",
441
  "resolved_at": "2025-10-27T19:22:12.440Z",
442
  "resolved_inferred": false,
443
  "started_at": "2025-10-27T14:29:13.482Z",
 
450
  "body": "This incident has been resolved.",
451
  "first_seen": "2026-09-04T07:06:16Z",
452
  "impact": "none",
453
+ "last_seen": "2026-09-04T14:19:03Z",
454
  "resolved_at": "2025-10-23T13:31:28.743Z",
455
  "resolved_inferred": false,
456
  "started_at": "2025-10-22T20:15:20.581Z",
 
463
  "body": "Over the weekend of monitoring, resolution for this incident has remained stable. This incident is resolved.",
464
  "first_seen": "2026-09-04T07:06:16Z",
465
  "impact": "minor",
466
+ "last_seen": "2026-09-04T14:19:03Z",
467
  "resolved_at": "2025-10-27T14:26:53.919Z",
468
  "resolved_inferred": false,
469
  "started_at": "2025-10-22T13:38:56.235Z",
 
476
  "body": "This incident has been resolved.",
477
  "first_seen": "2026-09-04T07:06:16Z",
478
  "impact": "minor",
479
+ "last_seen": "2026-09-04T14:19:03Z",
480
  "resolved_at": "2025-11-19T15:51:45.693Z",
481
  "resolved_inferred": false,
482
  "started_at": "2025-09-26T14:05:32.538Z",
 
489
  "body": "This incident has been resolved.",
490
  "first_seen": "2026-09-04T07:06:16Z",
491
  "impact": "major",
492
+ "last_seen": "2026-09-04T14:19:03Z",
493
  "resolved_at": "2025-09-26T20:02:34.263Z",
494
  "resolved_inferred": false,
495
  "started_at": "2025-09-23T19:27:04.877Z",
 
502
  "body": "This incident has been resolved.",
503
  "first_seen": "2026-09-04T07:06:16Z",
504
  "impact": "none",
505
+ "last_seen": "2026-09-04T14:19:03Z",
506
  "resolved_at": "2025-09-22T16:13:16.910Z",
507
  "resolved_inferred": false,
508
  "started_at": "2025-09-22T13:02:51.228Z",
 
515
  "body": "This incident has been resolved.",
516
  "first_seen": "2026-09-04T07:06:16Z",
517
  "impact": "minor",
518
+ "last_seen": "2026-09-04T14:19:03Z",
519
  "resolved_at": "2025-09-09T20:00:13.314Z",
520
  "resolved_inferred": false,
521
  "started_at": "2025-09-09T13:45:41.298Z",
 
528
  "body": "This incident has been resolved.",
529
  "first_seen": "2026-09-04T07:06:16Z",
530
  "impact": "minor",
531
+ "last_seen": "2026-09-04T14:19:03Z",
532
  "resolved_at": "2025-08-26T12:18:19.458Z",
533
  "resolved_inferred": false,
534
  "started_at": "2025-08-25T14:48:39.203Z",
 
541
  "body": "This incident has been resolved.",
542
  "first_seen": "2026-09-04T07:06:16Z",
543
  "impact": "none",
544
+ "last_seen": "2026-09-04T14:19:03Z",
545
  "resolved_at": "2025-08-19T16:22:20.005Z",
546
  "resolved_inferred": false,
547
  "started_at": "2025-08-19T16:06:00.582Z",
api/v/paribu.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "paribu",
4
  "platform": "statuspage",
5
  "status_url": "https://status.paribu.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "partial",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "Mina (MINA) a\u011f\u0131nda ger\u00e7ekle\u015fen g\u00fcncelleme nedeniyle Mina (MINA) yat\u0131rma ve \u00e7ekme i\u015flemleri ge\u00e7ici olarak durduruldu.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "maintenance",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "started_at": "2026-09-03T12:16:46.805+03:00",
17
  "state": "investigating",
18
  "title": "Mina (MINA) A\u011f G\u00fcncellemesi",
@@ -23,7 +23,7 @@
23
  "body": "Nesa (NES) kontrat\u0131nda ya\u015fanan aksakl\u0131k nedeniyle Nes (NESA) al\u0131m i\u015flemleri aray\u00fczde kapal\u0131d\u0131r.",
24
  "first_seen": "2026-09-04T07:06:16Z",
25
  "impact": "none",
26
- "last_seen": "2026-09-04T12:24:18Z",
27
  "started_at": "2026-08-28T16:06:06.689+03:00",
28
  "state": "investigating",
29
  "title": "Nesa (NES) DeFi Token\u0131 Al\u0131m ve Sat\u0131m \u0130\u015flemleri",
@@ -34,7 +34,7 @@
34
  "body": "TAC(TAC) kontrat\u0131nda ya\u015fanan aksakl\u0131k nedeniyle TAC (TAC) al\u0131m i\u015flemleri aray\u00fczde kapal\u0131d\u0131r.",
35
  "first_seen": "2026-09-04T07:06:16Z",
36
  "impact": "none",
37
- "last_seen": "2026-09-04T12:24:18Z",
38
  "started_at": "2026-08-28T16:05:09.801+03:00",
39
  "state": "investigating",
40
  "title": "TAC (TAC) DeFi Token\u0131 Al\u0131m ve Sat\u0131m \u0130\u015flemleri",
@@ -45,7 +45,7 @@
45
  "body": "Kite (KITE) yat\u0131rma ve \u00e7ekme i\u015flemleri a\u00e7\u0131ld\u0131.",
46
  "first_seen": "2026-09-04T07:06:16Z",
47
  "impact": "critical",
48
- "last_seen": "2026-09-04T12:24:18Z",
49
  "resolved_at": "2026-08-27T13:18:19.734+03:00",
50
  "resolved_inferred": false,
51
  "started_at": "2026-08-13T11:26:17.000+03:00",
@@ -58,7 +58,7 @@
58
  "body": "Ravencoin (RVN) yat\u0131rma ve \u00e7ekme i\u015flemleri a\u00e7\u0131ld\u0131.",
59
  "first_seen": "2026-09-04T07:06:16Z",
60
  "impact": "critical",
61
- "last_seen": "2026-09-04T12:24:18Z",
62
  "resolved_at": "2026-09-01T18:08:19.269+03:00",
63
  "resolved_inferred": false,
64
  "started_at": "2026-08-11T10:59:21.000+03:00",
@@ -71,7 +71,7 @@
71
  "body": "Bonk (BONK) yat\u0131rma i\u015flemleri a\u00e7\u0131ld\u0131.",
72
  "first_seen": "2026-09-04T07:06:16Z",
73
  "impact": "major",
74
- "last_seen": "2026-09-04T12:24:18Z",
75
  "resolved_at": "2026-07-08T14:38:41.619+03:00",
76
  "resolved_inferred": false,
77
  "started_at": "2026-07-06T21:27:53.171+03:00",
@@ -84,7 +84,7 @@
84
  "body": "Toncoin (TON) - Gram (GRAM) Token d\u00f6n\u00fc\u015f\u00fcm\u00fc tamamland\u0131. GRAM i\u015flemleri a\u00e7\u0131ld\u0131.",
85
  "first_seen": "2026-09-04T07:06:16Z",
86
  "impact": "maintenance",
87
- "last_seen": "2026-09-04T12:24:18Z",
88
  "resolved_at": "2026-07-09T19:57:18.452+03:00",
89
  "resolved_inferred": false,
90
  "started_at": "2026-07-06T12:00:09.057+03:00",
@@ -97,7 +97,7 @@
97
  "body": "Aksakl\u0131k \u00e7\u00f6z\u00fcmlendi.",
98
  "first_seen": "2026-09-04T07:06:16Z",
99
  "impact": "critical",
100
- "last_seen": "2026-09-04T12:24:18Z",
101
  "resolved_at": "2026-06-19T09:52:16.477+03:00",
102
  "resolved_inferred": false,
103
  "started_at": "2026-06-19T05:43:14.767+03:00",
@@ -110,7 +110,7 @@
110
  "body": "Humanity (H) kontrat\u0131nda ya\u015fanan aksakl\u0131k nedeniyle Humanity (H) yat\u0131rma ve \u00e7ekme i\u015flemleri kapal\u0131d\u0131r.",
111
  "first_seen": "2026-09-04T07:06:16Z",
112
  "impact": "critical",
113
- "last_seen": "2026-09-04T12:24:18Z",
114
  "started_at": "2026-06-10T17:45:34.440+03:00",
115
  "state": "investigating",
116
  "title": "Humanity (H) Yat\u0131rma ve \u00c7ekme \u0130\u015flemleri",
@@ -121,7 +121,7 @@
121
  "body": "G\u00fcncelleme tamamland\u0131.",
122
  "first_seen": "2026-09-04T07:06:16Z",
123
  "impact": "maintenance",
124
- "last_seen": "2026-09-04T12:24:18Z",
125
  "resolved_at": "2026-05-06T10:32:05.412+03:00",
126
  "resolved_inferred": false,
127
  "started_at": "2026-05-05T08:00:24.126+03:00",
@@ -134,7 +134,7 @@
134
  "body": "Bak\u0131m \u00e7al\u0131\u015fmas\u0131 tamamland\u0131.",
135
  "first_seen": "2026-09-04T07:06:16Z",
136
  "impact": "maintenance",
137
- "last_seen": "2026-09-04T12:24:18Z",
138
  "resolved_at": "2026-04-30T09:33:22.498+03:00",
139
  "resolved_inferred": false,
140
  "started_at": "2026-04-30T07:11:09.979+03:00",
@@ -147,7 +147,7 @@
147
  "body": "G\u00fcncelleme tamamland\u0131.",
148
  "first_seen": "2026-09-04T07:06:16Z",
149
  "impact": "maintenance",
150
- "last_seen": "2026-09-04T12:24:18Z",
151
  "resolved_at": "2026-04-29T09:07:01.376+03:00",
152
  "resolved_inferred": false,
153
  "started_at": "2026-04-28T16:37:12.252+03:00",
@@ -160,7 +160,7 @@
160
  "body": "G\u00fcncelleme tamamland\u0131.",
161
  "first_seen": "2026-09-04T07:06:16Z",
162
  "impact": "maintenance",
163
- "last_seen": "2026-09-04T12:24:18Z",
164
  "resolved_at": "2026-04-28T09:44:20.307+03:00",
165
  "resolved_inferred": false,
166
  "started_at": "2026-04-28T05:12:26.014+03:00",
@@ -173,7 +173,7 @@
173
  "body": "G\u00fcncelleme tamamland\u0131.",
174
  "first_seen": "2026-09-04T07:06:16Z",
175
  "impact": "maintenance",
176
- "last_seen": "2026-09-04T12:24:18Z",
177
  "resolved_at": "2026-05-06T11:02:25.210+03:00",
178
  "resolved_inferred": false,
179
  "started_at": "2026-04-27T12:19:21.559+03:00",
@@ -186,7 +186,7 @@
186
  "body": "Aksakl\u0131k \u00e7\u00f6z\u00fcmlendi.",
187
  "first_seen": "2026-09-04T07:06:16Z",
188
  "impact": "minor",
189
- "last_seen": "2026-09-04T12:24:18Z",
190
  "resolved_at": "2026-04-16T12:50:33.652+03:00",
191
  "resolved_inferred": false,
192
  "started_at": "2026-04-16T11:16:33.703+03:00",
@@ -199,7 +199,7 @@
199
  "body": "G\u00fcncelleme tamamland\u0131.",
200
  "first_seen": "2026-09-04T07:06:16Z",
201
  "impact": "maintenance",
202
- "last_seen": "2026-09-04T12:24:18Z",
203
  "resolved_at": "2026-04-15T17:33:04.253+03:00",
204
  "resolved_inferred": false,
205
  "started_at": "2026-04-15T16:31:08.544+03:00",
@@ -212,7 +212,7 @@
212
  "body": "G\u00fcncelleme tamamland\u0131.",
213
  "first_seen": "2026-09-04T07:06:16Z",
214
  "impact": "maintenance",
215
- "last_seen": "2026-09-04T12:24:18Z",
216
  "resolved_at": "2026-04-15T10:32:35.604+03:00",
217
  "resolved_inferred": false,
218
  "started_at": "2026-04-14T14:03:33.020+03:00",
@@ -225,7 +225,7 @@
225
  "body": "G\u00fcncelleme tamamland\u0131.",
226
  "first_seen": "2026-09-04T07:06:16Z",
227
  "impact": "maintenance",
228
- "last_seen": "2026-09-04T12:24:18Z",
229
  "resolved_at": "2026-04-13T13:40:52.538+03:00",
230
  "resolved_inferred": false,
231
  "started_at": "2026-04-13T11:16:33.391+03:00",
@@ -238,7 +238,7 @@
238
  "body": "G\u00fcncelleme tamanland\u0131.",
239
  "first_seen": "2026-09-04T07:06:16Z",
240
  "impact": "maintenance",
241
- "last_seen": "2026-09-04T12:24:18Z",
242
  "resolved_at": "2026-04-09T13:47:11.315+03:00",
243
  "resolved_inferred": false,
244
  "started_at": "2026-04-08T16:08:06.756+03:00",
@@ -251,7 +251,7 @@
251
  "body": "G\u00fcncelleme s\u00fcreci tamamland\u0131. Paribu servisleri ola\u011fan \u015fekilde \u00e7al\u0131\u015f\u0131yor. Anlay\u0131\u015f\u0131n\u0131z i\u00e7in te\u015fekk\u00fcr ederiz.",
252
  "first_seen": "2026-09-04T07:06:16Z",
253
  "impact": "minor",
254
- "last_seen": "2026-09-04T12:24:18Z",
255
  "resolved_at": "2026-04-08T12:26:00.646+03:00",
256
  "resolved_inferred": false,
257
  "started_at": "2026-04-08T04:14:09.410+03:00",
@@ -264,7 +264,7 @@
264
  "body": "G\u00fcncelleme tamamland\u0131.",
265
  "first_seen": "2026-09-04T07:06:16Z",
266
  "impact": "maintenance",
267
- "last_seen": "2026-09-04T12:24:18Z",
268
  "resolved_at": "2026-04-07T19:28:59.349+03:00",
269
  "resolved_inferred": false,
270
  "started_at": "2026-04-07T16:34:28.573+03:00",
@@ -277,7 +277,7 @@
277
  "body": "G\u00fcncelleme tamamland\u0131.",
278
  "first_seen": "2026-09-04T07:06:16Z",
279
  "impact": "maintenance",
280
- "last_seen": "2026-09-04T12:24:18Z",
281
  "resolved_at": "2026-04-01T18:46:50.019+03:00",
282
  "resolved_inferred": false,
283
  "started_at": "2026-04-01T17:02:19.697+03:00",
@@ -290,7 +290,7 @@
290
  "body": "Aksakl\u0131k giderildi",
291
  "first_seen": "2026-09-04T07:06:16Z",
292
  "impact": "minor",
293
- "last_seen": "2026-09-04T12:24:18Z",
294
  "resolved_at": "2026-03-26T13:43:42.158+03:00",
295
  "resolved_inferred": false,
296
  "started_at": "2026-03-26T09:26:59.180+03:00",
@@ -303,7 +303,7 @@
303
  "body": "Planl\u0131 bak\u0131m \u00e7al\u0131\u015fmas\u0131 tamamland\u0131.",
304
  "first_seen": "2026-09-04T07:06:16Z",
305
  "impact": "maintenance",
306
- "last_seen": "2026-09-04T12:24:18Z",
307
  "resolved_at": "2026-03-25T16:27:01.534+03:00",
308
  "resolved_inferred": false,
309
  "started_at": "2026-03-25T01:00:01.775+03:00",
@@ -316,7 +316,7 @@
316
  "body": "G\u00fcncelleme tamamland\u0131.",
317
  "first_seen": "2026-09-04T07:06:16Z",
318
  "impact": "maintenance",
319
- "last_seen": "2026-09-04T12:24:18Z",
320
  "resolved_at": "2026-03-23T18:15:55.432+03:00",
321
  "resolved_inferred": false,
322
  "started_at": "2026-03-23T14:32:31.953+03:00",
@@ -329,7 +329,7 @@
329
  "body": "G\u00fcncelleme tamamland\u0131",
330
  "first_seen": "2026-09-04T07:06:16Z",
331
  "impact": "maintenance",
332
- "last_seen": "2026-09-04T12:24:18Z",
333
  "resolved_at": "2026-03-20T01:08:11.000+03:00",
334
  "resolved_inferred": false,
335
  "started_at": "2026-03-19T16:30:07.438+03:00",
@@ -342,7 +342,7 @@
342
  "body": "Aksakl\u0131k giderildi.",
343
  "first_seen": "2026-09-04T07:06:16Z",
344
  "impact": "major",
345
- "last_seen": "2026-09-04T12:24:18Z",
346
  "resolved_at": "2026-03-15T22:42:04.232+03:00",
347
  "resolved_inferred": false,
348
  "started_at": "2026-03-15T14:19:43.879+03:00",
@@ -355,7 +355,7 @@
355
  "body": "Bak\u0131m \u00e7al\u0131\u015fmas\u0131 tamamland\u0131.",
356
  "first_seen": "2026-09-04T07:06:16Z",
357
  "impact": "maintenance",
358
- "last_seen": "2026-09-04T12:24:18Z",
359
  "resolved_at": "2026-03-13T08:22:28.603+03:00",
360
  "resolved_inferred": false,
361
  "started_at": "2026-03-13T07:08:50.607+03:00",
@@ -368,7 +368,7 @@
368
  "body": "G\u00fcncelleme tamamland\u0131",
369
  "first_seen": "2026-09-04T07:06:16Z",
370
  "impact": "maintenance",
371
- "last_seen": "2026-09-04T12:24:18Z",
372
  "resolved_at": "2026-03-13T07:13:08.000+03:00",
373
  "resolved_inferred": false,
374
  "started_at": "2026-03-11T16:02:53.396+03:00",
@@ -381,7 +381,7 @@
381
  "body": "G\u00fcncelleme tamamland\u0131",
382
  "first_seen": "2026-09-04T07:06:16Z",
383
  "impact": "maintenance",
384
- "last_seen": "2026-09-04T12:24:18Z",
385
  "resolved_at": "2026-03-09T18:01:16.946+03:00",
386
  "resolved_inferred": false,
387
  "started_at": "2026-03-09T16:06:46.597+03:00",
@@ -394,7 +394,7 @@
394
  "body": "G\u00fcncelleme tamamland\u0131.",
395
  "first_seen": "2026-09-04T07:06:16Z",
396
  "impact": "maintenance",
397
- "last_seen": "2026-09-04T12:24:18Z",
398
  "resolved_at": "2026-03-05T09:28:15.683+03:00",
399
  "resolved_inferred": false,
400
  "started_at": "2026-03-04T16:26:30.788+03:00",
@@ -407,7 +407,7 @@
407
  "body": "G\u00fcncelleme tamamland\u0131.",
408
  "first_seen": "2026-09-04T07:06:16Z",
409
  "impact": "maintenance",
410
- "last_seen": "2026-09-04T12:24:18Z",
411
  "resolved_at": "2026-03-04T18:01:23.687+03:00",
412
  "resolved_inferred": false,
413
  "started_at": "2026-03-04T16:25:04.326+03:00",
@@ -420,7 +420,7 @@
420
  "body": "G\u00fcncelleme tamamland\u0131",
421
  "first_seen": "2026-09-04T07:06:16Z",
422
  "impact": "maintenance",
423
- "last_seen": "2026-09-04T12:24:18Z",
424
  "resolved_at": "2026-03-05T13:20:03.326+03:00",
425
  "resolved_inferred": false,
426
  "started_at": "2026-03-03T13:13:10.041+03:00",
@@ -433,7 +433,7 @@
433
  "body": "Bak\u0131m \u00e7al\u0131\u015fmas\u0131 tamamland\u0131.",
434
  "first_seen": "2026-09-04T07:06:16Z",
435
  "impact": "maintenance",
436
- "last_seen": "2026-09-04T12:24:18Z",
437
  "resolved_at": "2026-02-22T06:21:06.216+03:00",
438
  "resolved_inferred": false,
439
  "started_at": "2026-02-22T04:02:29.069+03:00",
@@ -446,7 +446,7 @@
446
  "body": "Aksakl\u0131k giderildi",
447
  "first_seen": "2026-09-04T07:06:16Z",
448
  "impact": "minor",
449
- "last_seen": "2026-09-04T12:24:18Z",
450
  "resolved_at": "2026-02-20T09:28:33.201+03:00",
451
  "resolved_inferred": false,
452
  "started_at": "2026-02-19T21:59:10.590+03:00",
@@ -459,7 +459,7 @@
459
  "body": "Aksakl\u0131k giderildi",
460
  "first_seen": "2026-09-04T07:06:16Z",
461
  "impact": "minor",
462
- "last_seen": "2026-09-04T12:24:18Z",
463
  "resolved_at": "2026-02-20T09:56:03.776+03:00",
464
  "resolved_inferred": false,
465
  "started_at": "2026-02-19T17:08:26.190+03:00",
@@ -472,7 +472,7 @@
472
  "body": "Bak\u0131m \u00e7al\u0131\u015fmas\u0131 tamamland\u0131.",
473
  "first_seen": "2026-09-04T07:06:16Z",
474
  "impact": "maintenance",
475
- "last_seen": "2026-09-04T12:24:18Z",
476
  "resolved_at": "2026-02-19T15:44:41.291+03:00",
477
  "resolved_inferred": false,
478
  "started_at": "2026-02-19T12:55:48.019+03:00",
@@ -485,7 +485,7 @@
485
  "body": "G\u00fcncelleme tamamland\u0131.",
486
  "first_seen": "2026-09-04T07:06:16Z",
487
  "impact": "maintenance",
488
- "last_seen": "2026-09-04T12:24:18Z",
489
  "resolved_at": "2026-02-18T17:07:51.412+03:00",
490
  "resolved_inferred": false,
491
  "started_at": "2026-02-18T15:32:39.959+03:00",
@@ -498,7 +498,7 @@
498
  "body": "Aksakl\u0131k giderildi",
499
  "first_seen": "2026-09-04T07:06:16Z",
500
  "impact": "minor",
501
- "last_seen": "2026-09-04T12:24:18Z",
502
  "resolved_at": "2026-02-18T17:35:26.070+03:00",
503
  "resolved_inferred": false,
504
  "started_at": "2026-02-18T13:17:14.991+03:00",
@@ -511,7 +511,7 @@
511
  "body": "Aksakl\u0131k giderildi.",
512
  "first_seen": "2026-09-04T07:06:16Z",
513
  "impact": "none",
514
- "last_seen": "2026-09-04T12:24:18Z",
515
  "resolved_at": "2026-02-14T14:00:03.126+03:00",
516
  "resolved_inferred": false,
517
  "started_at": "2026-02-14T13:18:23.984+03:00",
@@ -524,7 +524,7 @@
524
  "body": "Bak\u0131m \u00e7al\u0131\u015fmas\u0131 tamamland\u0131.",
525
  "first_seen": "2026-09-04T07:06:16Z",
526
  "impact": "none",
527
- "last_seen": "2026-09-04T12:24:18Z",
528
  "resolved_at": "2026-02-10T08:13:57.817+03:00",
529
  "resolved_inferred": false,
530
  "started_at": "2026-02-10T05:37:39.937+03:00",
@@ -537,7 +537,7 @@
537
  "body": "G\u00fcncelleme tamamland\u0131.",
538
  "first_seen": "2026-09-04T07:06:16Z",
539
  "impact": "maintenance",
540
- "last_seen": "2026-09-04T12:24:18Z",
541
  "resolved_at": "2026-02-05T20:05:28.943+03:00",
542
  "resolved_inferred": false,
543
  "started_at": "2026-02-05T12:52:07.000+03:00",
@@ -550,7 +550,7 @@
550
  "body": "G\u00fcncelleme tamamland\u0131.",
551
  "first_seen": "2026-09-04T07:06:16Z",
552
  "impact": "maintenance",
553
- "last_seen": "2026-09-04T12:24:18Z",
554
  "resolved_at": "2026-02-03T22:14:09.360+03:00",
555
  "resolved_inferred": false,
556
  "started_at": "2026-02-03T16:54:43.246+03:00",
@@ -563,7 +563,7 @@
563
  "body": "G\u00fcncelleme tamamland\u0131",
564
  "first_seen": "2026-09-04T07:06:16Z",
565
  "impact": "maintenance",
566
- "last_seen": "2026-09-04T12:24:18Z",
567
  "resolved_at": "2026-01-30T17:37:01.185+03:00",
568
  "resolved_inferred": false,
569
  "started_at": "2026-01-29T19:07:35.165+03:00",
@@ -576,7 +576,7 @@
576
  "body": "Aksakl\u0131k giderildi",
577
  "first_seen": "2026-09-04T07:06:16Z",
578
  "impact": "major",
579
- "last_seen": "2026-09-04T12:24:18Z",
580
  "resolved_at": "2026-01-27T09:57:21.577+03:00",
581
  "resolved_inferred": false,
582
  "started_at": "2026-01-26T11:38:45.000+03:00",
@@ -589,7 +589,7 @@
589
  "body": "G\u00fcncelleme tamamland\u0131.",
590
  "first_seen": "2026-09-04T07:06:16Z",
591
  "impact": "maintenance",
592
- "last_seen": "2026-09-04T12:24:18Z",
593
  "resolved_at": "2026-01-26T11:51:18.759+03:00",
594
  "resolved_inferred": false,
595
  "started_at": "2026-01-22T20:03:45.354+03:00",
@@ -602,7 +602,7 @@
602
  "body": "G\u00fcncelleme tamamland\u0131.",
603
  "first_seen": "2026-09-04T07:06:16Z",
604
  "impact": "maintenance",
605
- "last_seen": "2026-09-04T12:24:18Z",
606
  "resolved_at": "2026-01-14T10:21:35.962+03:00",
607
  "resolved_inferred": false,
608
  "started_at": "2026-01-14T05:24:42.206+03:00",
@@ -615,7 +615,7 @@
615
  "body": "G\u00fcncelleme tamamland\u0131.",
616
  "first_seen": "2026-09-04T07:06:16Z",
617
  "impact": "maintenance",
618
- "last_seen": "2026-09-04T12:24:18Z",
619
  "resolved_at": "2026-01-12T19:49:59.344+03:00",
620
  "resolved_inferred": false,
621
  "started_at": "2026-01-12T17:03:08.232+03:00",
@@ -628,7 +628,7 @@
628
  "body": "Aksakl\u0131k giderildi",
629
  "first_seen": "2026-09-04T07:06:16Z",
630
  "impact": "maintenance",
631
- "last_seen": "2026-09-04T12:24:18Z",
632
  "resolved_at": "2025-12-18T19:05:27.825+03:00",
633
  "resolved_inferred": false,
634
  "started_at": "2025-12-18T18:37:04.000+03:00",
@@ -641,7 +641,7 @@
641
  "body": "G\u00fcncelleme tamamland\u0131.",
642
  "first_seen": "2026-09-04T07:06:16Z",
643
  "impact": "maintenance",
644
- "last_seen": "2026-09-04T12:24:18Z",
645
  "resolved_at": "2025-12-09T09:41:32.966+03:00",
646
  "resolved_inferred": false,
647
  "started_at": "2025-12-08T19:02:42.135+03:00",
 
3
  "slug": "paribu",
4
  "platform": "statuspage",
5
  "status_url": "https://status.paribu.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "partial",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "Mina (MINA) a\u011f\u0131nda ger\u00e7ekle\u015fen g\u00fcncelleme nedeniyle Mina (MINA) yat\u0131rma ve \u00e7ekme i\u015flemleri ge\u00e7ici olarak durduruldu.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "maintenance",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "started_at": "2026-09-03T12:16:46.805+03:00",
17
  "state": "investigating",
18
  "title": "Mina (MINA) A\u011f G\u00fcncellemesi",
 
23
  "body": "Nesa (NES) kontrat\u0131nda ya\u015fanan aksakl\u0131k nedeniyle Nes (NESA) al\u0131m i\u015flemleri aray\u00fczde kapal\u0131d\u0131r.",
24
  "first_seen": "2026-09-04T07:06:16Z",
25
  "impact": "none",
26
+ "last_seen": "2026-09-04T14:19:03Z",
27
  "started_at": "2026-08-28T16:06:06.689+03:00",
28
  "state": "investigating",
29
  "title": "Nesa (NES) DeFi Token\u0131 Al\u0131m ve Sat\u0131m \u0130\u015flemleri",
 
34
  "body": "TAC(TAC) kontrat\u0131nda ya\u015fanan aksakl\u0131k nedeniyle TAC (TAC) al\u0131m i\u015flemleri aray\u00fczde kapal\u0131d\u0131r.",
35
  "first_seen": "2026-09-04T07:06:16Z",
36
  "impact": "none",
37
+ "last_seen": "2026-09-04T14:19:03Z",
38
  "started_at": "2026-08-28T16:05:09.801+03:00",
39
  "state": "investigating",
40
  "title": "TAC (TAC) DeFi Token\u0131 Al\u0131m ve Sat\u0131m \u0130\u015flemleri",
 
45
  "body": "Kite (KITE) yat\u0131rma ve \u00e7ekme i\u015flemleri a\u00e7\u0131ld\u0131.",
46
  "first_seen": "2026-09-04T07:06:16Z",
47
  "impact": "critical",
48
+ "last_seen": "2026-09-04T14:19:03Z",
49
  "resolved_at": "2026-08-27T13:18:19.734+03:00",
50
  "resolved_inferred": false,
51
  "started_at": "2026-08-13T11:26:17.000+03:00",
 
58
  "body": "Ravencoin (RVN) yat\u0131rma ve \u00e7ekme i\u015flemleri a\u00e7\u0131ld\u0131.",
59
  "first_seen": "2026-09-04T07:06:16Z",
60
  "impact": "critical",
61
+ "last_seen": "2026-09-04T14:19:03Z",
62
  "resolved_at": "2026-09-01T18:08:19.269+03:00",
63
  "resolved_inferred": false,
64
  "started_at": "2026-08-11T10:59:21.000+03:00",
 
71
  "body": "Bonk (BONK) yat\u0131rma i\u015flemleri a\u00e7\u0131ld\u0131.",
72
  "first_seen": "2026-09-04T07:06:16Z",
73
  "impact": "major",
74
+ "last_seen": "2026-09-04T14:19:03Z",
75
  "resolved_at": "2026-07-08T14:38:41.619+03:00",
76
  "resolved_inferred": false,
77
  "started_at": "2026-07-06T21:27:53.171+03:00",
 
84
  "body": "Toncoin (TON) - Gram (GRAM) Token d\u00f6n\u00fc\u015f\u00fcm\u00fc tamamland\u0131. GRAM i\u015flemleri a\u00e7\u0131ld\u0131.",
85
  "first_seen": "2026-09-04T07:06:16Z",
86
  "impact": "maintenance",
87
+ "last_seen": "2026-09-04T14:19:03Z",
88
  "resolved_at": "2026-07-09T19:57:18.452+03:00",
89
  "resolved_inferred": false,
90
  "started_at": "2026-07-06T12:00:09.057+03:00",
 
97
  "body": "Aksakl\u0131k \u00e7\u00f6z\u00fcmlendi.",
98
  "first_seen": "2026-09-04T07:06:16Z",
99
  "impact": "critical",
100
+ "last_seen": "2026-09-04T14:19:03Z",
101
  "resolved_at": "2026-06-19T09:52:16.477+03:00",
102
  "resolved_inferred": false,
103
  "started_at": "2026-06-19T05:43:14.767+03:00",
 
110
  "body": "Humanity (H) kontrat\u0131nda ya\u015fanan aksakl\u0131k nedeniyle Humanity (H) yat\u0131rma ve \u00e7ekme i\u015flemleri kapal\u0131d\u0131r.",
111
  "first_seen": "2026-09-04T07:06:16Z",
112
  "impact": "critical",
113
+ "last_seen": "2026-09-04T14:19:03Z",
114
  "started_at": "2026-06-10T17:45:34.440+03:00",
115
  "state": "investigating",
116
  "title": "Humanity (H) Yat\u0131rma ve \u00c7ekme \u0130\u015flemleri",
 
121
  "body": "G\u00fcncelleme tamamland\u0131.",
122
  "first_seen": "2026-09-04T07:06:16Z",
123
  "impact": "maintenance",
124
+ "last_seen": "2026-09-04T14:19:03Z",
125
  "resolved_at": "2026-05-06T10:32:05.412+03:00",
126
  "resolved_inferred": false,
127
  "started_at": "2026-05-05T08:00:24.126+03:00",
 
134
  "body": "Bak\u0131m \u00e7al\u0131\u015fmas\u0131 tamamland\u0131.",
135
  "first_seen": "2026-09-04T07:06:16Z",
136
  "impact": "maintenance",
137
+ "last_seen": "2026-09-04T14:19:03Z",
138
  "resolved_at": "2026-04-30T09:33:22.498+03:00",
139
  "resolved_inferred": false,
140
  "started_at": "2026-04-30T07:11:09.979+03:00",
 
147
  "body": "G\u00fcncelleme tamamland\u0131.",
148
  "first_seen": "2026-09-04T07:06:16Z",
149
  "impact": "maintenance",
150
+ "last_seen": "2026-09-04T14:19:03Z",
151
  "resolved_at": "2026-04-29T09:07:01.376+03:00",
152
  "resolved_inferred": false,
153
  "started_at": "2026-04-28T16:37:12.252+03:00",
 
160
  "body": "G\u00fcncelleme tamamland\u0131.",
161
  "first_seen": "2026-09-04T07:06:16Z",
162
  "impact": "maintenance",
163
+ "last_seen": "2026-09-04T14:19:03Z",
164
  "resolved_at": "2026-04-28T09:44:20.307+03:00",
165
  "resolved_inferred": false,
166
  "started_at": "2026-04-28T05:12:26.014+03:00",
 
173
  "body": "G\u00fcncelleme tamamland\u0131.",
174
  "first_seen": "2026-09-04T07:06:16Z",
175
  "impact": "maintenance",
176
+ "last_seen": "2026-09-04T14:19:03Z",
177
  "resolved_at": "2026-05-06T11:02:25.210+03:00",
178
  "resolved_inferred": false,
179
  "started_at": "2026-04-27T12:19:21.559+03:00",
 
186
  "body": "Aksakl\u0131k \u00e7\u00f6z\u00fcmlendi.",
187
  "first_seen": "2026-09-04T07:06:16Z",
188
  "impact": "minor",
189
+ "last_seen": "2026-09-04T14:19:03Z",
190
  "resolved_at": "2026-04-16T12:50:33.652+03:00",
191
  "resolved_inferred": false,
192
  "started_at": "2026-04-16T11:16:33.703+03:00",
 
199
  "body": "G\u00fcncelleme tamamland\u0131.",
200
  "first_seen": "2026-09-04T07:06:16Z",
201
  "impact": "maintenance",
202
+ "last_seen": "2026-09-04T14:19:03Z",
203
  "resolved_at": "2026-04-15T17:33:04.253+03:00",
204
  "resolved_inferred": false,
205
  "started_at": "2026-04-15T16:31:08.544+03:00",
 
212
  "body": "G\u00fcncelleme tamamland\u0131.",
213
  "first_seen": "2026-09-04T07:06:16Z",
214
  "impact": "maintenance",
215
+ "last_seen": "2026-09-04T14:19:03Z",
216
  "resolved_at": "2026-04-15T10:32:35.604+03:00",
217
  "resolved_inferred": false,
218
  "started_at": "2026-04-14T14:03:33.020+03:00",
 
225
  "body": "G\u00fcncelleme tamamland\u0131.",
226
  "first_seen": "2026-09-04T07:06:16Z",
227
  "impact": "maintenance",
228
+ "last_seen": "2026-09-04T14:19:03Z",
229
  "resolved_at": "2026-04-13T13:40:52.538+03:00",
230
  "resolved_inferred": false,
231
  "started_at": "2026-04-13T11:16:33.391+03:00",
 
238
  "body": "G\u00fcncelleme tamanland\u0131.",
239
  "first_seen": "2026-09-04T07:06:16Z",
240
  "impact": "maintenance",
241
+ "last_seen": "2026-09-04T14:19:03Z",
242
  "resolved_at": "2026-04-09T13:47:11.315+03:00",
243
  "resolved_inferred": false,
244
  "started_at": "2026-04-08T16:08:06.756+03:00",
 
251
  "body": "G\u00fcncelleme s\u00fcreci tamamland\u0131. Paribu servisleri ola\u011fan \u015fekilde \u00e7al\u0131\u015f\u0131yor. Anlay\u0131\u015f\u0131n\u0131z i\u00e7in te\u015fekk\u00fcr ederiz.",
252
  "first_seen": "2026-09-04T07:06:16Z",
253
  "impact": "minor",
254
+ "last_seen": "2026-09-04T14:19:03Z",
255
  "resolved_at": "2026-04-08T12:26:00.646+03:00",
256
  "resolved_inferred": false,
257
  "started_at": "2026-04-08T04:14:09.410+03:00",
 
264
  "body": "G\u00fcncelleme tamamland\u0131.",
265
  "first_seen": "2026-09-04T07:06:16Z",
266
  "impact": "maintenance",
267
+ "last_seen": "2026-09-04T14:19:03Z",
268
  "resolved_at": "2026-04-07T19:28:59.349+03:00",
269
  "resolved_inferred": false,
270
  "started_at": "2026-04-07T16:34:28.573+03:00",
 
277
  "body": "G\u00fcncelleme tamamland\u0131.",
278
  "first_seen": "2026-09-04T07:06:16Z",
279
  "impact": "maintenance",
280
+ "last_seen": "2026-09-04T14:19:03Z",
281
  "resolved_at": "2026-04-01T18:46:50.019+03:00",
282
  "resolved_inferred": false,
283
  "started_at": "2026-04-01T17:02:19.697+03:00",
 
290
  "body": "Aksakl\u0131k giderildi",
291
  "first_seen": "2026-09-04T07:06:16Z",
292
  "impact": "minor",
293
+ "last_seen": "2026-09-04T14:19:03Z",
294
  "resolved_at": "2026-03-26T13:43:42.158+03:00",
295
  "resolved_inferred": false,
296
  "started_at": "2026-03-26T09:26:59.180+03:00",
 
303
  "body": "Planl\u0131 bak\u0131m \u00e7al\u0131\u015fmas\u0131 tamamland\u0131.",
304
  "first_seen": "2026-09-04T07:06:16Z",
305
  "impact": "maintenance",
306
+ "last_seen": "2026-09-04T14:19:03Z",
307
  "resolved_at": "2026-03-25T16:27:01.534+03:00",
308
  "resolved_inferred": false,
309
  "started_at": "2026-03-25T01:00:01.775+03:00",
 
316
  "body": "G\u00fcncelleme tamamland\u0131.",
317
  "first_seen": "2026-09-04T07:06:16Z",
318
  "impact": "maintenance",
319
+ "last_seen": "2026-09-04T14:19:03Z",
320
  "resolved_at": "2026-03-23T18:15:55.432+03:00",
321
  "resolved_inferred": false,
322
  "started_at": "2026-03-23T14:32:31.953+03:00",
 
329
  "body": "G\u00fcncelleme tamamland\u0131",
330
  "first_seen": "2026-09-04T07:06:16Z",
331
  "impact": "maintenance",
332
+ "last_seen": "2026-09-04T14:19:03Z",
333
  "resolved_at": "2026-03-20T01:08:11.000+03:00",
334
  "resolved_inferred": false,
335
  "started_at": "2026-03-19T16:30:07.438+03:00",
 
342
  "body": "Aksakl\u0131k giderildi.",
343
  "first_seen": "2026-09-04T07:06:16Z",
344
  "impact": "major",
345
+ "last_seen": "2026-09-04T14:19:03Z",
346
  "resolved_at": "2026-03-15T22:42:04.232+03:00",
347
  "resolved_inferred": false,
348
  "started_at": "2026-03-15T14:19:43.879+03:00",
 
355
  "body": "Bak\u0131m \u00e7al\u0131\u015fmas\u0131 tamamland\u0131.",
356
  "first_seen": "2026-09-04T07:06:16Z",
357
  "impact": "maintenance",
358
+ "last_seen": "2026-09-04T14:19:03Z",
359
  "resolved_at": "2026-03-13T08:22:28.603+03:00",
360
  "resolved_inferred": false,
361
  "started_at": "2026-03-13T07:08:50.607+03:00",
 
368
  "body": "G\u00fcncelleme tamamland\u0131",
369
  "first_seen": "2026-09-04T07:06:16Z",
370
  "impact": "maintenance",
371
+ "last_seen": "2026-09-04T14:19:03Z",
372
  "resolved_at": "2026-03-13T07:13:08.000+03:00",
373
  "resolved_inferred": false,
374
  "started_at": "2026-03-11T16:02:53.396+03:00",
 
381
  "body": "G\u00fcncelleme tamamland\u0131",
382
  "first_seen": "2026-09-04T07:06:16Z",
383
  "impact": "maintenance",
384
+ "last_seen": "2026-09-04T14:19:03Z",
385
  "resolved_at": "2026-03-09T18:01:16.946+03:00",
386
  "resolved_inferred": false,
387
  "started_at": "2026-03-09T16:06:46.597+03:00",
 
394
  "body": "G\u00fcncelleme tamamland\u0131.",
395
  "first_seen": "2026-09-04T07:06:16Z",
396
  "impact": "maintenance",
397
+ "last_seen": "2026-09-04T14:19:03Z",
398
  "resolved_at": "2026-03-05T09:28:15.683+03:00",
399
  "resolved_inferred": false,
400
  "started_at": "2026-03-04T16:26:30.788+03:00",
 
407
  "body": "G\u00fcncelleme tamamland\u0131.",
408
  "first_seen": "2026-09-04T07:06:16Z",
409
  "impact": "maintenance",
410
+ "last_seen": "2026-09-04T14:19:03Z",
411
  "resolved_at": "2026-03-04T18:01:23.687+03:00",
412
  "resolved_inferred": false,
413
  "started_at": "2026-03-04T16:25:04.326+03:00",
 
420
  "body": "G\u00fcncelleme tamamland\u0131",
421
  "first_seen": "2026-09-04T07:06:16Z",
422
  "impact": "maintenance",
423
+ "last_seen": "2026-09-04T14:19:03Z",
424
  "resolved_at": "2026-03-05T13:20:03.326+03:00",
425
  "resolved_inferred": false,
426
  "started_at": "2026-03-03T13:13:10.041+03:00",
 
433
  "body": "Bak\u0131m \u00e7al\u0131\u015fmas\u0131 tamamland\u0131.",
434
  "first_seen": "2026-09-04T07:06:16Z",
435
  "impact": "maintenance",
436
+ "last_seen": "2026-09-04T14:19:03Z",
437
  "resolved_at": "2026-02-22T06:21:06.216+03:00",
438
  "resolved_inferred": false,
439
  "started_at": "2026-02-22T04:02:29.069+03:00",
 
446
  "body": "Aksakl\u0131k giderildi",
447
  "first_seen": "2026-09-04T07:06:16Z",
448
  "impact": "minor",
449
+ "last_seen": "2026-09-04T14:19:03Z",
450
  "resolved_at": "2026-02-20T09:28:33.201+03:00",
451
  "resolved_inferred": false,
452
  "started_at": "2026-02-19T21:59:10.590+03:00",
 
459
  "body": "Aksakl\u0131k giderildi",
460
  "first_seen": "2026-09-04T07:06:16Z",
461
  "impact": "minor",
462
+ "last_seen": "2026-09-04T14:19:03Z",
463
  "resolved_at": "2026-02-20T09:56:03.776+03:00",
464
  "resolved_inferred": false,
465
  "started_at": "2026-02-19T17:08:26.190+03:00",
 
472
  "body": "Bak\u0131m \u00e7al\u0131\u015fmas\u0131 tamamland\u0131.",
473
  "first_seen": "2026-09-04T07:06:16Z",
474
  "impact": "maintenance",
475
+ "last_seen": "2026-09-04T14:19:03Z",
476
  "resolved_at": "2026-02-19T15:44:41.291+03:00",
477
  "resolved_inferred": false,
478
  "started_at": "2026-02-19T12:55:48.019+03:00",
 
485
  "body": "G\u00fcncelleme tamamland\u0131.",
486
  "first_seen": "2026-09-04T07:06:16Z",
487
  "impact": "maintenance",
488
+ "last_seen": "2026-09-04T14:19:03Z",
489
  "resolved_at": "2026-02-18T17:07:51.412+03:00",
490
  "resolved_inferred": false,
491
  "started_at": "2026-02-18T15:32:39.959+03:00",
 
498
  "body": "Aksakl\u0131k giderildi",
499
  "first_seen": "2026-09-04T07:06:16Z",
500
  "impact": "minor",
501
+ "last_seen": "2026-09-04T14:19:03Z",
502
  "resolved_at": "2026-02-18T17:35:26.070+03:00",
503
  "resolved_inferred": false,
504
  "started_at": "2026-02-18T13:17:14.991+03:00",
 
511
  "body": "Aksakl\u0131k giderildi.",
512
  "first_seen": "2026-09-04T07:06:16Z",
513
  "impact": "none",
514
+ "last_seen": "2026-09-04T14:19:03Z",
515
  "resolved_at": "2026-02-14T14:00:03.126+03:00",
516
  "resolved_inferred": false,
517
  "started_at": "2026-02-14T13:18:23.984+03:00",
 
524
  "body": "Bak\u0131m \u00e7al\u0131\u015fmas\u0131 tamamland\u0131.",
525
  "first_seen": "2026-09-04T07:06:16Z",
526
  "impact": "none",
527
+ "last_seen": "2026-09-04T14:19:03Z",
528
  "resolved_at": "2026-02-10T08:13:57.817+03:00",
529
  "resolved_inferred": false,
530
  "started_at": "2026-02-10T05:37:39.937+03:00",
 
537
  "body": "G\u00fcncelleme tamamland\u0131.",
538
  "first_seen": "2026-09-04T07:06:16Z",
539
  "impact": "maintenance",
540
+ "last_seen": "2026-09-04T14:19:03Z",
541
  "resolved_at": "2026-02-05T20:05:28.943+03:00",
542
  "resolved_inferred": false,
543
  "started_at": "2026-02-05T12:52:07.000+03:00",
 
550
  "body": "G\u00fcncelleme tamamland\u0131.",
551
  "first_seen": "2026-09-04T07:06:16Z",
552
  "impact": "maintenance",
553
+ "last_seen": "2026-09-04T14:19:03Z",
554
  "resolved_at": "2026-02-03T22:14:09.360+03:00",
555
  "resolved_inferred": false,
556
  "started_at": "2026-02-03T16:54:43.246+03:00",
 
563
  "body": "G\u00fcncelleme tamamland\u0131",
564
  "first_seen": "2026-09-04T07:06:16Z",
565
  "impact": "maintenance",
566
+ "last_seen": "2026-09-04T14:19:03Z",
567
  "resolved_at": "2026-01-30T17:37:01.185+03:00",
568
  "resolved_inferred": false,
569
  "started_at": "2026-01-29T19:07:35.165+03:00",
 
576
  "body": "Aksakl\u0131k giderildi",
577
  "first_seen": "2026-09-04T07:06:16Z",
578
  "impact": "major",
579
+ "last_seen": "2026-09-04T14:19:03Z",
580
  "resolved_at": "2026-01-27T09:57:21.577+03:00",
581
  "resolved_inferred": false,
582
  "started_at": "2026-01-26T11:38:45.000+03:00",
 
589
  "body": "G\u00fcncelleme tamamland\u0131.",
590
  "first_seen": "2026-09-04T07:06:16Z",
591
  "impact": "maintenance",
592
+ "last_seen": "2026-09-04T14:19:03Z",
593
  "resolved_at": "2026-01-26T11:51:18.759+03:00",
594
  "resolved_inferred": false,
595
  "started_at": "2026-01-22T20:03:45.354+03:00",
 
602
  "body": "G\u00fcncelleme tamamland\u0131.",
603
  "first_seen": "2026-09-04T07:06:16Z",
604
  "impact": "maintenance",
605
+ "last_seen": "2026-09-04T14:19:03Z",
606
  "resolved_at": "2026-01-14T10:21:35.962+03:00",
607
  "resolved_inferred": false,
608
  "started_at": "2026-01-14T05:24:42.206+03:00",
 
615
  "body": "G\u00fcncelleme tamamland\u0131.",
616
  "first_seen": "2026-09-04T07:06:16Z",
617
  "impact": "maintenance",
618
+ "last_seen": "2026-09-04T14:19:03Z",
619
  "resolved_at": "2026-01-12T19:49:59.344+03:00",
620
  "resolved_inferred": false,
621
  "started_at": "2026-01-12T17:03:08.232+03:00",
 
628
  "body": "Aksakl\u0131k giderildi",
629
  "first_seen": "2026-09-04T07:06:16Z",
630
  "impact": "maintenance",
631
+ "last_seen": "2026-09-04T14:19:03Z",
632
  "resolved_at": "2025-12-18T19:05:27.825+03:00",
633
  "resolved_inferred": false,
634
  "started_at": "2025-12-18T18:37:04.000+03:00",
 
641
  "body": "G\u00fcncelleme tamamland\u0131.",
642
  "first_seen": "2026-09-04T07:06:16Z",
643
  "impact": "maintenance",
644
+ "last_seen": "2026-09-04T14:19:03Z",
645
  "resolved_at": "2025-12-09T09:41:32.966+03:00",
646
  "resolved_inferred": false,
647
  "started_at": "2025-12-08T19:02:42.135+03:00",
api/v/particle.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "particle",
4
  "platform": "statuspage",
5
  "status_url": "https://status.particle.io",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved. All Tachyon devices have successfully reconnected and connectivity has been fully restored.\n\nOur team identified the root cause and implemented a fix, confirming full recovery across the affected fleet.\n\nNo other Particle device type or SKU was affected by this incident.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-09-01T16:01:46.683-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-01T13:48:15.097-07:00",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved. All Tachyon devices have successfully reconnected and connectivity has been fully restored.\n\nNo other Particle device type or SKU was affected by this incident.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-09-01T11:55:55.229-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-09-01T10:40:52.529-07:00",
@@ -38,7 +38,7 @@
38
  "body": "The issue is considered resolved. Affected devices will need to be reset or power cycled to resume connectivity.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-07-14T13:27:50.541-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-06-08T05:16:53.717-07:00",
@@ -51,7 +51,7 @@
51
  "body": "The issue impacting cellular connectivity on our MVNO network has been resolved. Services have remained stable following recovery, and our teams have confirmed normal operation across affected systems.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-05-21T13:17:50.337-07:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-05-21T08:07:21.114-07:00",
@@ -64,7 +64,7 @@
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-05-14T18:26:49.272-07:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-05-14T18:00:09.935-07:00",
@@ -77,7 +77,7 @@
77
  "body": "Particle has deployed a fix, and services are back to baseline.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-05-05T17:41:22.430-07:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-05-05T17:02:28.344-07:00",
@@ -90,7 +90,7 @@
90
  "body": "Connectivity has recovered.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-05-01T14:01:29.555-07:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-05-01T11:16:03.222-07:00",
@@ -103,7 +103,7 @@
103
  "body": "The issue was resolved",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-03-10T14:18:36.456-07:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-03-10T10:00:15.526-07:00",
@@ -116,7 +116,7 @@
116
  "body": "Connectivity has recovered to normal levels.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "none",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-03-08T04:39:13.103-07:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-03-08T00:15:27.823-08:00",
@@ -129,7 +129,7 @@
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "major",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-02-24T23:23:45.376-08:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-02-24T13:24:24.709-08:00",
@@ -142,7 +142,7 @@
142
  "body": "This incident has been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "minor",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2026-01-06T11:00:52.190-08:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-01-06T07:53:59.264-08:00",
@@ -155,7 +155,7 @@
155
  "body": "The incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "minor",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2025-10-21T03:51:54.606-07:00",
160
  "resolved_inferred": false,
161
  "started_at": "2025-10-20T12:47:23.645-07:00",
@@ -168,7 +168,7 @@
168
  "body": "Metrics for logic and integrations are back to normal.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2025-10-20T18:25:53.580-07:00",
173
  "resolved_inferred": false,
174
  "started_at": "2025-10-20T09:59:35.670-07:00",
@@ -181,7 +181,7 @@
181
  "body": "The incident has resolved and services are back to normal.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "none",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2025-10-20T06:53:04.865-07:00",
186
  "resolved_inferred": false,
187
  "started_at": "2025-10-20T03:35:12.498-07:00",
@@ -194,7 +194,7 @@
194
  "body": "Online devices count and behavior match our daily numbers.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2025-10-09T18:56:30.589-07:00",
199
  "resolved_inferred": false,
200
  "started_at": "2025-10-09T08:45:11.187-07:00",
@@ -207,7 +207,7 @@
207
  "body": "The incident was resolved. Fleet numbers reached pre-outage levels and are stable.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "major",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2025-09-28T07:54:50.964-07:00",
212
  "resolved_inferred": false,
213
  "started_at": "2025-09-28T06:56:35.878-07:00",
@@ -220,7 +220,7 @@
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2025-09-18T09:30:40.273-07:00",
225
  "resolved_inferred": false,
226
  "started_at": "2025-09-18T07:21:18.024-07:00",
@@ -233,7 +233,7 @@
233
  "body": "The provider solved the issue, and the fleet recovered to values similar to before the outage",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2025-08-18T03:24:12.789-07:00",
238
  "resolved_inferred": false,
239
  "started_at": "2025-08-17T23:48:33.030-07:00",
@@ -246,7 +246,7 @@
246
  "body": "The change has been rolled back, and the console is fully functional.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "minor",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2025-08-05T11:08:44.876-07:00",
251
  "resolved_inferred": false,
252
  "started_at": "2025-08-05T11:02:03.754-07:00",
 
3
  "slug": "particle",
4
  "platform": "statuspage",
5
  "status_url": "https://status.particle.io",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved. All Tachyon devices have successfully reconnected and connectivity has been fully restored.\n\nOur team identified the root cause and implemented a fix, confirming full recovery across the affected fleet.\n\nNo other Particle device type or SKU was affected by this incident.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-09-01T16:01:46.683-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-01T13:48:15.097-07:00",
 
25
  "body": "This incident has been resolved. All Tachyon devices have successfully reconnected and connectivity has been fully restored.\n\nNo other Particle device type or SKU was affected by this incident.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-09-01T11:55:55.229-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-09-01T10:40:52.529-07:00",
 
38
  "body": "The issue is considered resolved. Affected devices will need to be reset or power cycled to resume connectivity.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-07-14T13:27:50.541-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-06-08T05:16:53.717-07:00",
 
51
  "body": "The issue impacting cellular connectivity on our MVNO network has been resolved. Services have remained stable following recovery, and our teams have confirmed normal operation across affected systems.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-05-21T13:17:50.337-07:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-05-21T08:07:21.114-07:00",
 
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-05-14T18:26:49.272-07:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-05-14T18:00:09.935-07:00",
 
77
  "body": "Particle has deployed a fix, and services are back to baseline.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-05-05T17:41:22.430-07:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-05-05T17:02:28.344-07:00",
 
90
  "body": "Connectivity has recovered.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-05-01T14:01:29.555-07:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-05-01T11:16:03.222-07:00",
 
103
  "body": "The issue was resolved",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-03-10T14:18:36.456-07:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-03-10T10:00:15.526-07:00",
 
116
  "body": "Connectivity has recovered to normal levels.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "none",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-03-08T04:39:13.103-07:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-03-08T00:15:27.823-08:00",
 
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "major",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-02-24T23:23:45.376-08:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-02-24T13:24:24.709-08:00",
 
142
  "body": "This incident has been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "minor",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2026-01-06T11:00:52.190-08:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-01-06T07:53:59.264-08:00",
 
155
  "body": "The incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "minor",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2025-10-21T03:51:54.606-07:00",
160
  "resolved_inferred": false,
161
  "started_at": "2025-10-20T12:47:23.645-07:00",
 
168
  "body": "Metrics for logic and integrations are back to normal.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2025-10-20T18:25:53.580-07:00",
173
  "resolved_inferred": false,
174
  "started_at": "2025-10-20T09:59:35.670-07:00",
 
181
  "body": "The incident has resolved and services are back to normal.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "none",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2025-10-20T06:53:04.865-07:00",
186
  "resolved_inferred": false,
187
  "started_at": "2025-10-20T03:35:12.498-07:00",
 
194
  "body": "Online devices count and behavior match our daily numbers.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2025-10-09T18:56:30.589-07:00",
199
  "resolved_inferred": false,
200
  "started_at": "2025-10-09T08:45:11.187-07:00",
 
207
  "body": "The incident was resolved. Fleet numbers reached pre-outage levels and are stable.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "major",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2025-09-28T07:54:50.964-07:00",
212
  "resolved_inferred": false,
213
  "started_at": "2025-09-28T06:56:35.878-07:00",
 
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2025-09-18T09:30:40.273-07:00",
225
  "resolved_inferred": false,
226
  "started_at": "2025-09-18T07:21:18.024-07:00",
 
233
  "body": "The provider solved the issue, and the fleet recovered to values similar to before the outage",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2025-08-18T03:24:12.789-07:00",
238
  "resolved_inferred": false,
239
  "started_at": "2025-08-17T23:48:33.030-07:00",
 
246
  "body": "The change has been rolled back, and the console is fully functional.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "minor",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2025-08-05T11:08:44.876-07:00",
251
  "resolved_inferred": false,
252
  "started_at": "2025-08-05T11:02:03.754-07:00",
api/v/pax8.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "pax8",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pax8.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-08-06T01:56:36.014-06:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-06T00:25:10.019-06:00",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-07-13T12:35:55.367-06:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-07-13T10:21:39.000-06:00",
@@ -38,7 +38,7 @@
38
  "body": "This issue has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-07-08T08:23:44.642-06:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-07-08T03:30:04.977-06:00",
@@ -51,7 +51,7 @@
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-05-22T07:13:56.276-06:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-05-21T14:37:09.747-06:00",
@@ -64,7 +64,7 @@
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "critical",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-04-23T17:32:40.308-06:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-04-23T15:32:12.614-06:00",
@@ -77,7 +77,7 @@
77
  "body": "This is was resolved 9:02PM MT Thursday 4/2/2026.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-04-03T11:55:10.497-06:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-04-01T12:43:18.474-06:00",
@@ -90,7 +90,7 @@
90
  "body": "We can confirm the checkout loading state issue has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-03-31T18:03:14.869-06:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-03-31T15:14:27.200-06:00",
@@ -103,7 +103,7 @@
103
  "body": "A fix has been implemented, and we are monitoring results.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-03-20T14:51:11.082-06:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-03-20T12:58:26.144-06:00",
@@ -116,7 +116,7 @@
116
  "body": "This incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "maintenance",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-03-03T07:45:47.883-07:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-01-13T14:29:17.356-07:00",
@@ -129,7 +129,7 @@
129
  "body": "We are back to normal behavior.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2025-12-02T14:52:18.986-07:00",
134
  "resolved_inferred": false,
135
  "started_at": "2025-12-02T07:27:37.396-07:00",
@@ -142,7 +142,7 @@
142
  "body": "We have confirmed that the Microsoft Customer Agreement issues have been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "minor",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2025-12-02T07:40:06.630-07:00",
147
  "resolved_inferred": false,
148
  "started_at": "2025-12-01T09:34:15.650-07:00",
@@ -155,7 +155,7 @@
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "major",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2025-10-29T18:45:38.811-06:00",
160
  "resolved_inferred": false,
161
  "started_at": "2025-10-29T10:58:49.266-06:00",
@@ -168,7 +168,7 @@
168
  "body": "AWS has resolved the incident on their side, and Pax8 is no longer observing any health concerns in our systems. We will now be closing this incident and will continue to monitor to ensure all services remain stable.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2025-10-20T18:41:18.372-06:00",
173
  "resolved_inferred": false,
174
  "started_at": "2025-10-20T03:58:44.168-06:00",
@@ -181,7 +181,7 @@
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "minor",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2025-10-10T16:34:05.386-06:00",
186
  "resolved_inferred": false,
187
  "started_at": "2025-10-10T10:25:25.455-06:00",
@@ -194,7 +194,7 @@
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "major",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2025-08-22T11:48:28.971-06:00",
199
  "resolved_inferred": false,
200
  "started_at": "2025-08-22T11:04:09.365-06:00",
 
3
  "slug": "pax8",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pax8.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-08-06T01:56:36.014-06:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-06T00:25:10.019-06:00",
 
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-07-13T12:35:55.367-06:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-07-13T10:21:39.000-06:00",
 
38
  "body": "This issue has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-07-08T08:23:44.642-06:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-07-08T03:30:04.977-06:00",
 
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-05-22T07:13:56.276-06:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-05-21T14:37:09.747-06:00",
 
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "critical",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-04-23T17:32:40.308-06:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-04-23T15:32:12.614-06:00",
 
77
  "body": "This is was resolved 9:02PM MT Thursday 4/2/2026.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-04-03T11:55:10.497-06:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-04-01T12:43:18.474-06:00",
 
90
  "body": "We can confirm the checkout loading state issue has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-03-31T18:03:14.869-06:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-03-31T15:14:27.200-06:00",
 
103
  "body": "A fix has been implemented, and we are monitoring results.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-03-20T14:51:11.082-06:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-03-20T12:58:26.144-06:00",
 
116
  "body": "This incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "maintenance",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-03-03T07:45:47.883-07:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-01-13T14:29:17.356-07:00",
 
129
  "body": "We are back to normal behavior.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2025-12-02T14:52:18.986-07:00",
134
  "resolved_inferred": false,
135
  "started_at": "2025-12-02T07:27:37.396-07:00",
 
142
  "body": "We have confirmed that the Microsoft Customer Agreement issues have been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "minor",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2025-12-02T07:40:06.630-07:00",
147
  "resolved_inferred": false,
148
  "started_at": "2025-12-01T09:34:15.650-07:00",
 
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "major",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2025-10-29T18:45:38.811-06:00",
160
  "resolved_inferred": false,
161
  "started_at": "2025-10-29T10:58:49.266-06:00",
 
168
  "body": "AWS has resolved the incident on their side, and Pax8 is no longer observing any health concerns in our systems. We will now be closing this incident and will continue to monitor to ensure all services remain stable.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2025-10-20T18:41:18.372-06:00",
173
  "resolved_inferred": false,
174
  "started_at": "2025-10-20T03:58:44.168-06:00",
 
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "minor",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2025-10-10T16:34:05.386-06:00",
186
  "resolved_inferred": false,
187
  "started_at": "2025-10-10T10:25:25.455-06:00",
 
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "major",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2025-08-22T11:48:28.971-06:00",
199
  "resolved_inferred": false,
200
  "started_at": "2025-08-22T11:04:09.365-06:00",
api/v/paycor.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "paycor",
4
  "platform": "statuspage",
5
  "status_url": "https://status.recruitingbypaycor.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "none",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-06-30T12:51:52.850-04:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-06-30T11:25:52.654-04:00",
@@ -25,7 +25,7 @@
25
  "body": "This incident is resolved and all transferred hires are appearing in the New Hire bucket in Onboarding.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-06-26T11:42:59.225-04:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-06-25T14:14:55.787-04:00",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-05-15T19:18:25.464-04:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-05-15T12:13:12.478-04:00",
@@ -51,7 +51,7 @@
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "critical",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-03-02T13:03:18.033-05:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-03-02T10:19:55.831-05:00",
@@ -64,7 +64,7 @@
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-01-02T18:44:38.777-05:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-01-02T14:06:37.316-05:00",
@@ -77,7 +77,7 @@
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2025-12-04T02:03:01.835-05:00",
82
  "resolved_inferred": false,
83
  "started_at": "2025-12-03T09:46:37.962-05:00",
@@ -90,7 +90,7 @@
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2025-10-10T09:27:47.617-04:00",
95
  "resolved_inferred": false,
96
  "started_at": "2025-10-09T15:56:59.817-04:00",
 
3
  "slug": "paycor",
4
  "platform": "statuspage",
5
  "status_url": "https://status.recruitingbypaycor.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "none",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-06-30T12:51:52.850-04:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-06-30T11:25:52.654-04:00",
 
25
  "body": "This incident is resolved and all transferred hires are appearing in the New Hire bucket in Onboarding.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-06-26T11:42:59.225-04:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-06-25T14:14:55.787-04:00",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-05-15T19:18:25.464-04:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-05-15T12:13:12.478-04:00",
 
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "critical",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-03-02T13:03:18.033-05:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-03-02T10:19:55.831-05:00",
 
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-01-02T18:44:38.777-05:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-01-02T14:06:37.316-05:00",
 
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2025-12-04T02:03:01.835-05:00",
82
  "resolved_inferred": false,
83
  "started_at": "2025-12-03T09:46:37.962-05:00",
 
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2025-10-10T09:27:47.617-04:00",
95
  "resolved_inferred": false,
96
  "started_at": "2025-10-09T15:56:59.817-04:00",
api/v/payoneer.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "payoneer",
4
  "platform": "statuspage",
5
  "status_url": "https://status.payoneer.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-08-03T17:53:10.051+03:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-03T16:13:59.344+03:00",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-06-18T14:43:05.863+03:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-06-18T14:14:31.799+03:00",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "major",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-06-15T15:43:16.914+03:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-06-15T15:18:49.828+03:00",
@@ -51,7 +51,7 @@
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-06-11T18:42:51.058+03:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-06-11T16:59:21.590+03:00",
@@ -64,7 +64,7 @@
64
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "critical",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-04-02T22:49:30.450+03:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-04-02T20:47:36.888+03:00",
@@ -77,7 +77,7 @@
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "critical",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-03-12T14:46:42.339+02:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-03-12T13:24:16.633+02:00",
@@ -90,7 +90,7 @@
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "critical",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-03-03T10:54:42.168+02:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-03-03T09:01:05.733+02:00",
@@ -103,7 +103,7 @@
103
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "critical",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-02-23T16:08:20.146+02:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-02-23T16:04:41.407+02:00",
@@ -116,7 +116,7 @@
116
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "critical",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-02-23T16:07:33.334+02:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-02-23T16:04:41.145+02:00",
@@ -129,7 +129,7 @@
129
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "critical",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-02-23T16:08:53.559+02:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-02-23T16:04:40.872+02:00",
@@ -142,7 +142,7 @@
142
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "critical",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2026-02-23T15:58:03.929+02:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-02-23T15:52:10.777+02:00",
@@ -155,7 +155,7 @@
155
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "critical",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2026-02-23T15:53:02.015+02:00",
160
  "resolved_inferred": false,
161
  "started_at": "2026-02-23T15:52:10.551+02:00",
@@ -168,7 +168,7 @@
168
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "critical",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2026-02-23T15:47:39.682+02:00",
173
  "resolved_inferred": false,
174
  "started_at": "2026-02-23T15:46:18.318+02:00",
@@ -181,7 +181,7 @@
181
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "critical",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2026-02-23T15:44:03.574+02:00",
186
  "resolved_inferred": false,
187
  "started_at": "2026-02-23T15:42:28.889+02:00",
@@ -194,7 +194,7 @@
194
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "critical",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2026-02-23T15:36:46.912+02:00",
199
  "resolved_inferred": false,
200
  "started_at": "2026-02-23T15:35:53.841+02:00",
@@ -207,7 +207,7 @@
207
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "critical",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2026-02-23T15:55:26.648+02:00",
212
  "resolved_inferred": false,
213
  "started_at": "2026-02-23T15:35:53.571+02:00",
@@ -220,7 +220,7 @@
220
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "critical",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2026-02-23T15:28:31.189+02:00",
225
  "resolved_inferred": false,
226
  "started_at": "2026-02-23T15:27:14.261+02:00",
@@ -233,7 +233,7 @@
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "critical",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2026-02-23T16:49:15.743+02:00",
238
  "resolved_inferred": false,
239
  "started_at": "2026-02-23T15:16:50.460+02:00",
@@ -246,7 +246,7 @@
246
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2026-02-23T15:11:11.558+02:00",
251
  "resolved_inferred": false,
252
  "started_at": "2026-02-23T15:09:32.269+02:00",
@@ -259,7 +259,7 @@
259
  "body": "This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "major",
262
- "last_seen": "2026-09-04T12:24:18Z",
263
  "resolved_at": "2026-02-11T12:35:59.286+02:00",
264
  "resolved_inferred": false,
265
  "started_at": "2026-02-11T10:57:38.476+02:00",
@@ -272,7 +272,7 @@
272
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "major",
275
- "last_seen": "2026-09-04T12:24:18Z",
276
  "resolved_at": "2025-12-15T14:39:27.019+02:00",
277
  "resolved_inferred": false,
278
  "started_at": "2025-12-15T10:21:17.487+02:00",
@@ -285,7 +285,7 @@
285
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "major",
288
- "last_seen": "2026-09-04T12:24:18Z",
289
  "resolved_at": "2025-12-13T09:18:22.326+02:00",
290
  "resolved_inferred": false,
291
  "started_at": "2025-12-13T09:16:48.770+02:00",
@@ -298,7 +298,7 @@
298
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "major",
301
- "last_seen": "2026-09-04T12:24:18Z",
302
  "resolved_at": "2025-12-13T09:18:19.617+02:00",
303
  "resolved_inferred": false,
304
  "started_at": "2025-12-13T09:16:48.522+02:00",
@@ -311,7 +311,7 @@
311
  "body": "This incident has been resolved.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "major",
314
- "last_seen": "2026-09-04T12:24:18Z",
315
  "resolved_at": "2025-12-11T20:12:29.425+02:00",
316
  "resolved_inferred": false,
317
  "started_at": "2025-12-11T16:50:01.916+02:00",
@@ -324,7 +324,7 @@
324
  "body": "This incident has been resolved.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "major",
327
- "last_seen": "2026-09-04T12:24:18Z",
328
  "resolved_at": "2025-12-09T10:50:25.874+02:00",
329
  "resolved_inferred": false,
330
  "started_at": "2025-12-09T09:28:55.372+02:00",
@@ -337,7 +337,7 @@
337
  "body": "This incident has been resolved.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "major",
340
- "last_seen": "2026-09-04T12:24:18Z",
341
  "resolved_at": "2025-11-19T10:45:58.495+02:00",
342
  "resolved_inferred": false,
343
  "started_at": "2025-11-19T09:14:11.608+02:00",
@@ -350,7 +350,7 @@
350
  "body": "This incident has been resolved.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "major",
353
- "last_seen": "2026-09-04T12:24:18Z",
354
  "resolved_at": "2025-11-11T14:41:04.347+02:00",
355
  "resolved_inferred": false,
356
  "started_at": "2025-11-11T13:19:43.327+02:00",
@@ -363,7 +363,7 @@
363
  "body": "This incident has been resolved.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "major",
366
- "last_seen": "2026-09-04T12:24:18Z",
367
  "resolved_at": "2025-11-06T15:39:09.122+02:00",
368
  "resolved_inferred": false,
369
  "started_at": "2025-11-05T17:27:38.965+02:00",
@@ -376,7 +376,7 @@
376
  "body": "This incident has been resolved.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "minor",
379
- "last_seen": "2026-09-04T12:24:18Z",
380
  "resolved_at": "2025-10-30T16:28:36.058+02:00",
381
  "resolved_inferred": false,
382
  "started_at": "2025-10-30T15:53:33.805+02:00",
@@ -389,7 +389,7 @@
389
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "major",
392
- "last_seen": "2026-09-04T12:24:18Z",
393
  "resolved_at": "2025-10-08T17:25:56.781+03:00",
394
  "resolved_inferred": false,
395
  "started_at": "2025-10-08T10:59:18.701+03:00",
@@ -402,7 +402,7 @@
402
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "major",
405
- "last_seen": "2026-09-04T12:24:18Z",
406
  "resolved_at": "2025-10-08T11:08:21.279+03:00",
407
  "resolved_inferred": false,
408
  "started_at": "2025-10-08T10:57:04.841+03:00",
@@ -415,7 +415,7 @@
415
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "critical",
418
- "last_seen": "2026-09-04T12:24:18Z",
419
  "resolved_at": "2025-09-28T14:50:01.676+03:00",
420
  "resolved_inferred": false,
421
  "started_at": "2025-09-28T11:42:53.171+03:00",
@@ -428,7 +428,7 @@
428
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "major",
431
- "last_seen": "2026-09-04T12:24:18Z",
432
  "resolved_at": "2025-09-08T14:42:06.448+03:00",
433
  "resolved_inferred": false,
434
  "started_at": "2025-09-08T11:49:35.496+03:00",
@@ -441,7 +441,7 @@
441
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "major",
444
- "last_seen": "2026-09-04T12:24:18Z",
445
  "resolved_at": "2025-08-27T21:05:33.746+03:00",
446
  "resolved_inferred": false,
447
  "started_at": "2025-08-27T19:39:55.336+03:00",
@@ -454,7 +454,7 @@
454
  "body": "This incident has been resolved.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "major",
457
- "last_seen": "2026-09-04T12:24:18Z",
458
  "resolved_at": "2025-08-13T14:25:42.047+03:00",
459
  "resolved_inferred": false,
460
  "started_at": "2025-08-13T12:52:21.279+03:00",
@@ -467,7 +467,7 @@
467
  "body": "This incident has been resolved.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "major",
470
- "last_seen": "2026-09-04T12:24:18Z",
471
  "resolved_at": "2025-08-13T14:25:54.601+03:00",
472
  "resolved_inferred": false,
473
  "started_at": "2025-08-13T12:22:42.863+03:00",
@@ -480,7 +480,7 @@
480
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "major",
483
- "last_seen": "2026-09-04T12:24:18Z",
484
  "resolved_at": "2025-08-01T14:48:10.778+03:00",
485
  "resolved_inferred": false,
486
  "started_at": "2025-08-01T13:29:47.521+03:00",
 
3
  "slug": "payoneer",
4
  "platform": "statuspage",
5
  "status_url": "https://status.payoneer.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-08-03T17:53:10.051+03:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-03T16:13:59.344+03:00",
 
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-06-18T14:43:05.863+03:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-06-18T14:14:31.799+03:00",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "major",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-06-15T15:43:16.914+03:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-06-15T15:18:49.828+03:00",
 
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-06-11T18:42:51.058+03:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-06-11T16:59:21.590+03:00",
 
64
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "critical",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-04-02T22:49:30.450+03:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-04-02T20:47:36.888+03:00",
 
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "critical",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-03-12T14:46:42.339+02:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-03-12T13:24:16.633+02:00",
 
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "critical",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-03-03T10:54:42.168+02:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-03-03T09:01:05.733+02:00",
 
103
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "critical",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-02-23T16:08:20.146+02:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-02-23T16:04:41.407+02:00",
 
116
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "critical",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-02-23T16:07:33.334+02:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-02-23T16:04:41.145+02:00",
 
129
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "critical",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-02-23T16:08:53.559+02:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-02-23T16:04:40.872+02:00",
 
142
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "critical",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2026-02-23T15:58:03.929+02:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-02-23T15:52:10.777+02:00",
 
155
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "critical",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2026-02-23T15:53:02.015+02:00",
160
  "resolved_inferred": false,
161
  "started_at": "2026-02-23T15:52:10.551+02:00",
 
168
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "critical",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2026-02-23T15:47:39.682+02:00",
173
  "resolved_inferred": false,
174
  "started_at": "2026-02-23T15:46:18.318+02:00",
 
181
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "critical",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2026-02-23T15:44:03.574+02:00",
186
  "resolved_inferred": false,
187
  "started_at": "2026-02-23T15:42:28.889+02:00",
 
194
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "critical",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2026-02-23T15:36:46.912+02:00",
199
  "resolved_inferred": false,
200
  "started_at": "2026-02-23T15:35:53.841+02:00",
 
207
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "critical",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2026-02-23T15:55:26.648+02:00",
212
  "resolved_inferred": false,
213
  "started_at": "2026-02-23T15:35:53.571+02:00",
 
220
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "critical",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2026-02-23T15:28:31.189+02:00",
225
  "resolved_inferred": false,
226
  "started_at": "2026-02-23T15:27:14.261+02:00",
 
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "critical",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2026-02-23T16:49:15.743+02:00",
238
  "resolved_inferred": false,
239
  "started_at": "2026-02-23T15:16:50.460+02:00",
 
246
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2026-02-23T15:11:11.558+02:00",
251
  "resolved_inferred": false,
252
  "started_at": "2026-02-23T15:09:32.269+02:00",
 
259
  "body": "This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "major",
262
+ "last_seen": "2026-09-04T14:19:03Z",
263
  "resolved_at": "2026-02-11T12:35:59.286+02:00",
264
  "resolved_inferred": false,
265
  "started_at": "2026-02-11T10:57:38.476+02:00",
 
272
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "major",
275
+ "last_seen": "2026-09-04T14:19:03Z",
276
  "resolved_at": "2025-12-15T14:39:27.019+02:00",
277
  "resolved_inferred": false,
278
  "started_at": "2025-12-15T10:21:17.487+02:00",
 
285
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "major",
288
+ "last_seen": "2026-09-04T14:19:03Z",
289
  "resolved_at": "2025-12-13T09:18:22.326+02:00",
290
  "resolved_inferred": false,
291
  "started_at": "2025-12-13T09:16:48.770+02:00",
 
298
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "major",
301
+ "last_seen": "2026-09-04T14:19:03Z",
302
  "resolved_at": "2025-12-13T09:18:19.617+02:00",
303
  "resolved_inferred": false,
304
  "started_at": "2025-12-13T09:16:48.522+02:00",
 
311
  "body": "This incident has been resolved.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "major",
314
+ "last_seen": "2026-09-04T14:19:03Z",
315
  "resolved_at": "2025-12-11T20:12:29.425+02:00",
316
  "resolved_inferred": false,
317
  "started_at": "2025-12-11T16:50:01.916+02:00",
 
324
  "body": "This incident has been resolved.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "major",
327
+ "last_seen": "2026-09-04T14:19:03Z",
328
  "resolved_at": "2025-12-09T10:50:25.874+02:00",
329
  "resolved_inferred": false,
330
  "started_at": "2025-12-09T09:28:55.372+02:00",
 
337
  "body": "This incident has been resolved.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "major",
340
+ "last_seen": "2026-09-04T14:19:03Z",
341
  "resolved_at": "2025-11-19T10:45:58.495+02:00",
342
  "resolved_inferred": false,
343
  "started_at": "2025-11-19T09:14:11.608+02:00",
 
350
  "body": "This incident has been resolved.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "major",
353
+ "last_seen": "2026-09-04T14:19:03Z",
354
  "resolved_at": "2025-11-11T14:41:04.347+02:00",
355
  "resolved_inferred": false,
356
  "started_at": "2025-11-11T13:19:43.327+02:00",
 
363
  "body": "This incident has been resolved.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "major",
366
+ "last_seen": "2026-09-04T14:19:03Z",
367
  "resolved_at": "2025-11-06T15:39:09.122+02:00",
368
  "resolved_inferred": false,
369
  "started_at": "2025-11-05T17:27:38.965+02:00",
 
376
  "body": "This incident has been resolved.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "minor",
379
+ "last_seen": "2026-09-04T14:19:03Z",
380
  "resolved_at": "2025-10-30T16:28:36.058+02:00",
381
  "resolved_inferred": false,
382
  "started_at": "2025-10-30T15:53:33.805+02:00",
 
389
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "major",
392
+ "last_seen": "2026-09-04T14:19:03Z",
393
  "resolved_at": "2025-10-08T17:25:56.781+03:00",
394
  "resolved_inferred": false,
395
  "started_at": "2025-10-08T10:59:18.701+03:00",
 
402
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "major",
405
+ "last_seen": "2026-09-04T14:19:03Z",
406
  "resolved_at": "2025-10-08T11:08:21.279+03:00",
407
  "resolved_inferred": false,
408
  "started_at": "2025-10-08T10:57:04.841+03:00",
 
415
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "critical",
418
+ "last_seen": "2026-09-04T14:19:03Z",
419
  "resolved_at": "2025-09-28T14:50:01.676+03:00",
420
  "resolved_inferred": false,
421
  "started_at": "2025-09-28T11:42:53.171+03:00",
 
428
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "major",
431
+ "last_seen": "2026-09-04T14:19:03Z",
432
  "resolved_at": "2025-09-08T14:42:06.448+03:00",
433
  "resolved_inferred": false,
434
  "started_at": "2025-09-08T11:49:35.496+03:00",
 
441
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "major",
444
+ "last_seen": "2026-09-04T14:19:03Z",
445
  "resolved_at": "2025-08-27T21:05:33.746+03:00",
446
  "resolved_inferred": false,
447
  "started_at": "2025-08-27T19:39:55.336+03:00",
 
454
  "body": "This incident has been resolved.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "major",
457
+ "last_seen": "2026-09-04T14:19:03Z",
458
  "resolved_at": "2025-08-13T14:25:42.047+03:00",
459
  "resolved_inferred": false,
460
  "started_at": "2025-08-13T12:52:21.279+03:00",
 
467
  "body": "This incident has been resolved.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "major",
470
+ "last_seen": "2026-09-04T14:19:03Z",
471
  "resolved_at": "2025-08-13T14:25:54.601+03:00",
472
  "resolved_inferred": false,
473
  "started_at": "2025-08-13T12:22:42.863+03:00",
 
480
  "body": "This incident has been resolved. \r\nWe apologize for any inconvenience.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "major",
483
+ "last_seen": "2026-09-04T14:19:03Z",
484
  "resolved_at": "2025-08-01T14:48:10.778+03:00",
485
  "resolved_inferred": false,
486
  "started_at": "2025-08-01T13:29:47.521+03:00",
api/v/payscale.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "payscale",
4
  "platform": "statuspage",
5
  "status_url": "https://status.payscale.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-06-23T10:24:47.015-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-06-23T10:07:31.307-07:00",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-01-09T12:00:08.720-08:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-01-08T10:05:53.246-08:00",
@@ -38,7 +38,7 @@
38
  "body": "Between 11:49 PM PDT on October 19 and 3:01 PM PDT on October 20, Marketpay experienced an interruption due to an issue with Amazon Web Services (AWS). Service has been fully restored, and systems are operating as expected.\n\nWe will continue to monitor performance to ensure stability.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "major",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2025-10-21T05:21:06.000-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2025-10-20T12:34:27.000-07:00",
 
3
  "slug": "payscale",
4
  "platform": "statuspage",
5
  "status_url": "https://status.payscale.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-06-23T10:24:47.015-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-06-23T10:07:31.307-07:00",
 
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-01-09T12:00:08.720-08:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-01-08T10:05:53.246-08:00",
 
38
  "body": "Between 11:49 PM PDT on October 19 and 3:01 PM PDT on October 20, Marketpay experienced an interruption due to an issue with Amazon Web Services (AWS). Service has been fully restored, and systems are operating as expected.\n\nWe will continue to monitor performance to ensure stability.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "major",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2025-10-21T05:21:06.000-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2025-10-20T12:34:27.000-07:00",
api/v/pdq.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "pdq",
4
  "platform": "statuspage",
5
  "status_url": "https://pdq.statuspage.io",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "degraded",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "Vulnerability updates are currently taking longer than expected to appear due to an unusually high volume of software vendor releases. We are actively monitoring the delay and working to improve processing times.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "started_at": "2026-09-03T12:47:59.345-04:00",
17
  "state": "monitoring",
18
  "title": "Connect - Delayed Vulnerability Updates",
@@ -23,7 +23,7 @@
23
  "body": "If \"Secure Attention Sequence\" is enabled in Group Policy, it must be set to \"Ease of Access applications\" in order for Connect to simulate \"Ctrl + Alt + Del\"",
24
  "first_seen": "2026-09-04T07:06:16Z",
25
  "impact": "major",
26
- "last_seen": "2026-09-04T12:24:18Z",
27
  "resolved_at": "2026-08-27T21:08:38.306-04:00",
28
  "resolved_inferred": false,
29
  "started_at": "2026-08-27T19:15:48.830-04:00",
@@ -36,7 +36,7 @@
36
  "body": "This incident has been resolved.",
37
  "first_seen": "2026-09-04T07:06:16Z",
38
  "impact": "minor",
39
- "last_seen": "2026-09-04T12:24:18Z",
40
  "resolved_at": "2026-08-26T10:56:17.587-04:00",
41
  "resolved_inferred": false,
42
  "started_at": "2026-08-26T10:36:27.297-04:00",
@@ -49,7 +49,7 @@
49
  "body": "This incident has been resolved.",
50
  "first_seen": "2026-09-04T07:06:16Z",
51
  "impact": "none",
52
- "last_seen": "2026-09-04T12:24:18Z",
53
  "resolved_at": "2026-08-25T22:25:24.656-04:00",
54
  "resolved_inferred": false,
55
  "started_at": "2026-08-25T18:35:37.411-04:00",
@@ -62,7 +62,7 @@
62
  "body": "This incident has been resolved.",
63
  "first_seen": "2026-09-04T07:06:16Z",
64
  "impact": "minor",
65
- "last_seen": "2026-09-04T12:24:18Z",
66
  "resolved_at": "2026-08-24T16:13:44.545-04:00",
67
  "resolved_inferred": false,
68
  "started_at": "2026-08-24T12:01:42.783-04:00",
@@ -75,7 +75,7 @@
75
  "body": "This incident has been resolved.",
76
  "first_seen": "2026-09-04T07:06:16Z",
77
  "impact": "minor",
78
- "last_seen": "2026-09-04T12:24:18Z",
79
  "resolved_at": "2026-08-15T10:58:29.504-04:00",
80
  "resolved_inferred": false,
81
  "started_at": "2026-08-12T09:19:43.982-04:00",
@@ -88,7 +88,7 @@
88
  "body": "This incident has been resolved.",
89
  "first_seen": "2026-09-04T07:06:16Z",
90
  "impact": "minor",
91
- "last_seen": "2026-09-04T12:24:18Z",
92
  "resolved_at": "2026-08-10T18:53:11.876-04:00",
93
  "resolved_inferred": false,
94
  "started_at": "2026-08-10T14:57:55.000-04:00",
@@ -101,7 +101,7 @@
101
  "body": "This incident has been resolved.",
102
  "first_seen": "2026-09-04T07:06:16Z",
103
  "impact": "critical",
104
- "last_seen": "2026-09-04T12:24:18Z",
105
  "resolved_at": "2026-08-05T10:53:09.201-04:00",
106
  "resolved_inferred": false,
107
  "started_at": "2026-08-05T10:44:01.472-04:00",
@@ -114,7 +114,7 @@
114
  "body": "This incident has been resolved.",
115
  "first_seen": "2026-09-04T07:06:16Z",
116
  "impact": "minor",
117
- "last_seen": "2026-09-04T12:24:18Z",
118
  "resolved_at": "2026-08-06T12:46:06.425-04:00",
119
  "resolved_inferred": false,
120
  "started_at": "2026-08-04T17:26:47.919-04:00",
@@ -127,7 +127,7 @@
127
  "body": "This incident has been resolved.",
128
  "first_seen": "2026-09-04T07:06:16Z",
129
  "impact": "minor",
130
- "last_seen": "2026-09-04T12:24:18Z",
131
  "resolved_at": "2026-07-30T13:10:30.239-04:00",
132
  "resolved_inferred": false,
133
  "started_at": "2026-07-30T12:11:31.229-04:00",
@@ -140,7 +140,7 @@
140
  "body": "All device scans have caught up and are up to date.",
141
  "first_seen": "2026-09-04T07:06:16Z",
142
  "impact": "minor",
143
- "last_seen": "2026-09-04T12:24:18Z",
144
  "resolved_at": "2026-07-28T23:34:34.949-04:00",
145
  "resolved_inferred": false,
146
  "started_at": "2026-07-28T10:11:29.951-04:00",
@@ -153,7 +153,7 @@
153
  "body": "This incident has been resolved.",
154
  "first_seen": "2026-09-04T07:06:16Z",
155
  "impact": "minor",
156
- "last_seen": "2026-09-04T12:24:18Z",
157
  "resolved_at": "2026-07-27T19:45:18.836-04:00",
158
  "resolved_inferred": false,
159
  "started_at": "2026-07-27T18:15:42.632-04:00",
@@ -166,7 +166,7 @@
166
  "body": "Users were unable to sign up for new trial accounts through the homepage.",
167
  "first_seen": "2026-09-04T07:06:16Z",
168
  "impact": "none",
169
- "last_seen": "2026-09-04T12:24:18Z",
170
  "resolved_at": "2026-07-27T10:41:00.000-04:00",
171
  "resolved_inferred": false,
172
  "started_at": "2026-07-27T10:41:00.000-04:00",
@@ -179,7 +179,7 @@
179
  "body": "This incident has been resolved.",
180
  "first_seen": "2026-09-04T07:06:16Z",
181
  "impact": "minor",
182
- "last_seen": "2026-09-04T12:24:18Z",
183
  "resolved_at": "2026-07-23T22:36:08.371-04:00",
184
  "resolved_inferred": false,
185
  "started_at": "2026-07-23T17:54:23.365-04:00",
@@ -192,7 +192,7 @@
192
  "body": "This incident has been resolved.",
193
  "first_seen": "2026-09-04T07:06:16Z",
194
  "impact": "minor",
195
- "last_seen": "2026-09-04T12:24:18Z",
196
  "resolved_at": "2026-07-20T17:30:35.095-04:00",
197
  "resolved_inferred": false,
198
  "started_at": "2026-07-20T10:47:04.432-04:00",
@@ -205,7 +205,7 @@
205
  "body": "This incident has been resolved.",
206
  "first_seen": "2026-09-04T07:06:16Z",
207
  "impact": "minor",
208
- "last_seen": "2026-09-04T12:24:18Z",
209
  "resolved_at": "2026-07-15T19:15:40.875-04:00",
210
  "resolved_inferred": false,
211
  "started_at": "2026-07-14T16:21:56.877-04:00",
@@ -218,7 +218,7 @@
218
  "body": "This incident has been resolved.",
219
  "first_seen": "2026-09-04T07:06:16Z",
220
  "impact": "minor",
221
- "last_seen": "2026-09-04T12:24:18Z",
222
  "resolved_at": "2026-06-17T10:06:02.545-04:00",
223
  "resolved_inferred": false,
224
  "started_at": "2026-06-17T09:33:16.822-04:00",
@@ -231,7 +231,7 @@
231
  "body": "This incident has been resolved.",
232
  "first_seen": "2026-09-04T07:06:16Z",
233
  "impact": "major",
234
- "last_seen": "2026-09-04T12:24:18Z",
235
  "resolved_at": "2026-06-11T22:02:49.804-04:00",
236
  "resolved_inferred": false,
237
  "started_at": "2026-06-11T19:54:54.099-04:00",
@@ -244,7 +244,7 @@
244
  "body": "This incident is resolved scans are working as expected now.",
245
  "first_seen": "2026-09-04T07:06:16Z",
246
  "impact": "major",
247
- "last_seen": "2026-09-04T12:24:18Z",
248
  "resolved_at": "2026-06-10T20:20:33.085-04:00",
249
  "resolved_inferred": false,
250
  "started_at": "2026-06-10T17:50:20.923-04:00",
@@ -257,7 +257,7 @@
257
  "body": "Connect was temporarily unavailable from about ~2:50 PM MDT to ~3:06 PM MDT",
258
  "first_seen": "2026-09-04T07:06:16Z",
259
  "impact": "none",
260
- "last_seen": "2026-09-04T12:24:18Z",
261
  "resolved_at": "2026-06-03T17:41:17.551-04:00",
262
  "resolved_inferred": false,
263
  "started_at": "2026-06-03T17:41:17.516-04:00",
@@ -270,7 +270,7 @@
270
  "body": "This incident has been resolved.",
271
  "first_seen": "2026-09-04T07:06:16Z",
272
  "impact": "minor",
273
- "last_seen": "2026-09-04T12:24:18Z",
274
  "resolved_at": "2026-06-02T18:55:39.071-04:00",
275
  "resolved_inferred": false,
276
  "started_at": "2026-06-02T15:35:22.000-04:00",
@@ -283,7 +283,7 @@
283
  "body": "This incident has been resolved.",
284
  "first_seen": "2026-09-04T07:06:16Z",
285
  "impact": "minor",
286
- "last_seen": "2026-09-04T12:24:18Z",
287
  "resolved_at": "2026-05-11T13:53:56.880-04:00",
288
  "resolved_inferred": false,
289
  "started_at": "2026-05-11T10:23:39.450-04:00",
@@ -296,7 +296,7 @@
296
  "body": "This incident has been resolved.",
297
  "first_seen": "2026-09-04T07:06:16Z",
298
  "impact": "minor",
299
- "last_seen": "2026-09-04T12:24:18Z",
300
  "resolved_at": "2026-05-07T13:01:04.775-04:00",
301
  "resolved_inferred": false,
302
  "started_at": "2026-05-07T10:59:05.120-04:00",
@@ -309,7 +309,7 @@
309
  "body": "This incident has been resolved.",
310
  "first_seen": "2026-09-04T07:06:16Z",
311
  "impact": "critical",
312
- "last_seen": "2026-09-04T12:24:18Z",
313
  "resolved_at": "2026-04-18T00:07:38.226-04:00",
314
  "resolved_inferred": false,
315
  "started_at": "2026-04-16T23:48:37.284-04:00",
@@ -322,7 +322,7 @@
322
  "body": "This incident has been resolved.",
323
  "first_seen": "2026-09-04T07:06:16Z",
324
  "impact": "critical",
325
- "last_seen": "2026-09-04T12:24:18Z",
326
  "resolved_at": "2026-04-16T14:18:43.570-04:00",
327
  "resolved_inferred": false,
328
  "started_at": "2026-04-16T12:59:58.063-04:00",
@@ -335,7 +335,7 @@
335
  "body": "All delays have now caught up and group counts are up to date.",
336
  "first_seen": "2026-09-04T07:06:16Z",
337
  "impact": "minor",
338
- "last_seen": "2026-09-04T12:24:18Z",
339
  "resolved_at": "2026-04-09T17:00:10.659-04:00",
340
  "resolved_inferred": false,
341
  "started_at": "2026-04-09T13:02:35.747-04:00",
@@ -348,7 +348,7 @@
348
  "body": "This incident has been resolved.",
349
  "first_seen": "2026-09-04T07:06:16Z",
350
  "impact": "major",
351
- "last_seen": "2026-09-04T12:24:18Z",
352
  "resolved_at": "2026-03-31T13:16:43.301-04:00",
353
  "resolved_inferred": false,
354
  "started_at": "2026-03-31T12:23:41.955-04:00",
@@ -361,7 +361,7 @@
361
  "body": "This incident has been resolved.",
362
  "first_seen": "2026-09-04T07:06:16Z",
363
  "impact": "critical",
364
- "last_seen": "2026-09-04T12:24:18Z",
365
  "resolved_at": "2026-03-26T16:58:22.293-04:00",
366
  "resolved_inferred": false,
367
  "started_at": "2026-03-26T16:30:29.000-04:00",
@@ -374,7 +374,7 @@
374
  "body": "This incident has been resolved.",
375
  "first_seen": "2026-09-04T07:06:16Z",
376
  "impact": "minor",
377
- "last_seen": "2026-09-04T12:24:18Z",
378
  "resolved_at": "2026-03-25T02:21:08.694-04:00",
379
  "resolved_inferred": false,
380
  "started_at": "2026-03-24T12:47:25.264-04:00",
@@ -387,7 +387,7 @@
387
  "body": "This incident has been resolved.",
388
  "first_seen": "2026-09-04T07:06:16Z",
389
  "impact": "minor",
390
- "last_seen": "2026-09-04T12:24:18Z",
391
  "resolved_at": "2026-03-16T16:02:58.989-04:00",
392
  "resolved_inferred": false,
393
  "started_at": "2026-03-16T09:54:24.894-04:00",
@@ -400,7 +400,7 @@
400
  "body": "This incident has been resolved.",
401
  "first_seen": "2026-09-04T07:06:16Z",
402
  "impact": "minor",
403
- "last_seen": "2026-09-04T12:24:18Z",
404
  "resolved_at": "2026-03-13T17:57:56.555-04:00",
405
  "resolved_inferred": false,
406
  "started_at": "2026-03-13T17:09:55.263-04:00",
@@ -413,7 +413,7 @@
413
  "body": "This incident has been resolved.",
414
  "first_seen": "2026-09-04T07:06:16Z",
415
  "impact": "minor",
416
- "last_seen": "2026-09-04T12:24:18Z",
417
  "resolved_at": "2026-03-13T15:35:04.538-04:00",
418
  "resolved_inferred": false,
419
  "started_at": "2026-03-13T13:25:05.911-04:00",
@@ -426,7 +426,7 @@
426
  "body": "This incident has been resolved.",
427
  "first_seen": "2026-09-04T07:06:16Z",
428
  "impact": "critical",
429
- "last_seen": "2026-09-04T12:24:18Z",
430
  "resolved_at": "2026-03-12T16:51:05.989-04:00",
431
  "resolved_inferred": false,
432
  "started_at": "2026-03-12T12:30:08.000-04:00",
@@ -439,7 +439,7 @@
439
  "body": "This incident has been resolved.",
440
  "first_seen": "2026-09-04T07:06:16Z",
441
  "impact": "minor",
442
- "last_seen": "2026-09-04T12:24:18Z",
443
  "resolved_at": "2026-03-11T12:28:18.984-04:00",
444
  "resolved_inferred": false,
445
  "started_at": "2026-03-11T10:56:04.122-04:00",
@@ -452,7 +452,7 @@
452
  "body": "We have resolved an issue with our metrics. This incident should have displayed no impact to customers.",
453
  "first_seen": "2026-09-04T07:06:16Z",
454
  "impact": "none",
455
- "last_seen": "2026-09-04T12:24:18Z",
456
  "resolved_at": "2026-03-07T14:04:21.454-05:00",
457
  "resolved_inferred": false,
458
  "started_at": "2026-03-07T13:31:43.564-05:00",
@@ -465,7 +465,7 @@
465
  "body": "This incident has been resolved.",
466
  "first_seen": "2026-09-04T07:06:16Z",
467
  "impact": "none",
468
- "last_seen": "2026-09-04T12:24:18Z",
469
  "resolved_at": "2026-02-20T00:53:12.367-05:00",
470
  "resolved_inferred": false,
471
  "started_at": "2026-02-19T23:35:53.984-05:00",
@@ -478,7 +478,7 @@
478
  "body": "This incident has been resolved.",
479
  "first_seen": "2026-09-04T07:06:16Z",
480
  "impact": "minor",
481
- "last_seen": "2026-09-04T12:24:18Z",
482
  "resolved_at": "2026-02-19T14:09:31.623-05:00",
483
  "resolved_inferred": false,
484
  "started_at": "2026-02-19T11:02:33.308-05:00",
@@ -491,7 +491,7 @@
491
  "body": "This incident has been resolved.",
492
  "first_seen": "2026-09-04T07:06:16Z",
493
  "impact": "minor",
494
- "last_seen": "2026-09-04T12:24:18Z",
495
  "resolved_at": "2026-02-16T18:11:39.877-05:00",
496
  "resolved_inferred": false,
497
  "started_at": "2026-02-16T16:39:33.988-05:00",
@@ -504,7 +504,7 @@
504
  "body": "Queues have all caught up and deployments are operational.",
505
  "first_seen": "2026-09-04T07:06:16Z",
506
  "impact": "minor",
507
- "last_seen": "2026-09-04T12:24:18Z",
508
  "resolved_at": "2026-02-12T14:05:44.209-05:00",
509
  "resolved_inferred": false,
510
  "started_at": "2026-02-12T12:02:20.263-05:00",
@@ -517,7 +517,7 @@
517
  "body": "Authentication remains stable and we're confident in resolving the issue at this time.",
518
  "first_seen": "2026-09-04T07:06:16Z",
519
  "impact": "critical",
520
- "last_seen": "2026-09-04T12:24:18Z",
521
  "resolved_at": "2026-02-12T10:08:05.488-05:00",
522
  "resolved_inferred": false,
523
  "started_at": "2026-02-11T09:37:49.603-05:00",
@@ -530,7 +530,7 @@
530
  "body": "This incident has been resolved.",
531
  "first_seen": "2026-09-04T07:06:16Z",
532
  "impact": "major",
533
- "last_seen": "2026-09-04T12:24:18Z",
534
  "resolved_at": "2026-01-28T14:27:55.750-05:00",
535
  "resolved_inferred": false,
536
  "started_at": "2026-01-27T15:29:00.208-05:00",
@@ -543,7 +543,7 @@
543
  "body": "Our email provider is reporting that the incident is fully resolved.",
544
  "first_seen": "2026-09-04T07:06:16Z",
545
  "impact": "minor",
546
- "last_seen": "2026-09-04T12:24:18Z",
547
  "resolved_at": "2026-02-02T10:40:41.941-05:00",
548
  "resolved_inferred": false,
549
  "started_at": "2026-01-23T11:06:29.559-05:00",
@@ -556,7 +556,7 @@
556
  "body": "We've determined that deployments are indeed running and that this is a UI bug. We're going to address this issue during normal business hours on Monday.",
557
  "first_seen": "2026-09-04T07:06:16Z",
558
  "impact": "minor",
559
- "last_seen": "2026-09-04T12:24:18Z",
560
  "resolved_at": "2026-01-23T11:10:48.748-05:00",
561
  "resolved_inferred": false,
562
  "started_at": "2026-01-23T10:27:25.505-05:00",
@@ -569,7 +569,7 @@
569
  "body": "Microsoft reports that this issue has been resolved.",
570
  "first_seen": "2026-09-04T07:06:16Z",
571
  "impact": "major",
572
- "last_seen": "2026-09-04T12:24:18Z",
573
  "resolved_at": "2026-01-23T09:06:36.018-05:00",
574
  "resolved_inferred": false,
575
  "started_at": "2026-01-22T16:04:46.000-05:00",
@@ -582,7 +582,7 @@
582
  "body": "This incident has been resolved.",
583
  "first_seen": "2026-09-04T07:06:16Z",
584
  "impact": "minor",
585
- "last_seen": "2026-09-04T12:24:18Z",
586
  "resolved_at": "2026-01-21T12:53:29.014-05:00",
587
  "resolved_inferred": false,
588
  "started_at": "2026-01-21T10:27:39.303-05:00",
@@ -595,7 +595,7 @@
595
  "body": "This incident has been resolved.",
596
  "first_seen": "2026-09-04T07:06:16Z",
597
  "impact": "critical",
598
- "last_seen": "2026-09-04T12:24:18Z",
599
  "resolved_at": "2026-01-20T16:27:42.914-05:00",
600
  "resolved_inferred": false,
601
  "started_at": "2026-01-20T09:20:28.265-05:00",
@@ -608,7 +608,7 @@
608
  "body": "This incident has been resolved.",
609
  "first_seen": "2026-09-04T07:06:16Z",
610
  "impact": "minor",
611
- "last_seen": "2026-09-04T12:24:18Z",
612
  "resolved_at": "2026-01-14T15:04:26.727-05:00",
613
  "resolved_inferred": false,
614
  "started_at": "2026-01-14T10:55:26.211-05:00",
@@ -621,7 +621,7 @@
621
  "body": "This incident has been resolved.",
622
  "first_seen": "2026-09-04T07:06:16Z",
623
  "impact": "minor",
624
- "last_seen": "2026-09-04T12:24:18Z",
625
  "resolved_at": "2026-01-13T14:08:08.965-05:00",
626
  "resolved_inferred": false,
627
  "started_at": "2026-01-13T11:30:26.000-05:00",
@@ -634,7 +634,7 @@
634
  "body": "This incident has been resolved.",
635
  "first_seen": "2026-09-04T07:06:16Z",
636
  "impact": "minor",
637
- "last_seen": "2026-09-04T12:24:18Z",
638
  "resolved_at": "2026-01-12T18:10:18.408-05:00",
639
  "resolved_inferred": false,
640
  "started_at": "2026-01-12T10:12:43.771-05:00",
@@ -647,7 +647,7 @@
647
  "body": "After monitoring we are not seeing any more delays",
648
  "first_seen": "2026-09-04T07:06:16Z",
649
  "impact": "minor",
650
- "last_seen": "2026-09-04T12:24:18Z",
651
  "resolved_at": "2025-12-15T17:04:36.331-05:00",
652
  "resolved_inferred": false,
653
  "started_at": "2025-12-15T13:19:04.406-05:00",
 
3
  "slug": "pdq",
4
  "platform": "statuspage",
5
  "status_url": "https://pdq.statuspage.io",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "degraded",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "Vulnerability updates are currently taking longer than expected to appear due to an unusually high volume of software vendor releases. We are actively monitoring the delay and working to improve processing times.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "started_at": "2026-09-03T12:47:59.345-04:00",
17
  "state": "monitoring",
18
  "title": "Connect - Delayed Vulnerability Updates",
 
23
  "body": "If \"Secure Attention Sequence\" is enabled in Group Policy, it must be set to \"Ease of Access applications\" in order for Connect to simulate \"Ctrl + Alt + Del\"",
24
  "first_seen": "2026-09-04T07:06:16Z",
25
  "impact": "major",
26
+ "last_seen": "2026-09-04T14:19:03Z",
27
  "resolved_at": "2026-08-27T21:08:38.306-04:00",
28
  "resolved_inferred": false,
29
  "started_at": "2026-08-27T19:15:48.830-04:00",
 
36
  "body": "This incident has been resolved.",
37
  "first_seen": "2026-09-04T07:06:16Z",
38
  "impact": "minor",
39
+ "last_seen": "2026-09-04T14:19:03Z",
40
  "resolved_at": "2026-08-26T10:56:17.587-04:00",
41
  "resolved_inferred": false,
42
  "started_at": "2026-08-26T10:36:27.297-04:00",
 
49
  "body": "This incident has been resolved.",
50
  "first_seen": "2026-09-04T07:06:16Z",
51
  "impact": "none",
52
+ "last_seen": "2026-09-04T14:19:03Z",
53
  "resolved_at": "2026-08-25T22:25:24.656-04:00",
54
  "resolved_inferred": false,
55
  "started_at": "2026-08-25T18:35:37.411-04:00",
 
62
  "body": "This incident has been resolved.",
63
  "first_seen": "2026-09-04T07:06:16Z",
64
  "impact": "minor",
65
+ "last_seen": "2026-09-04T14:19:03Z",
66
  "resolved_at": "2026-08-24T16:13:44.545-04:00",
67
  "resolved_inferred": false,
68
  "started_at": "2026-08-24T12:01:42.783-04:00",
 
75
  "body": "This incident has been resolved.",
76
  "first_seen": "2026-09-04T07:06:16Z",
77
  "impact": "minor",
78
+ "last_seen": "2026-09-04T14:19:03Z",
79
  "resolved_at": "2026-08-15T10:58:29.504-04:00",
80
  "resolved_inferred": false,
81
  "started_at": "2026-08-12T09:19:43.982-04:00",
 
88
  "body": "This incident has been resolved.",
89
  "first_seen": "2026-09-04T07:06:16Z",
90
  "impact": "minor",
91
+ "last_seen": "2026-09-04T14:19:03Z",
92
  "resolved_at": "2026-08-10T18:53:11.876-04:00",
93
  "resolved_inferred": false,
94
  "started_at": "2026-08-10T14:57:55.000-04:00",
 
101
  "body": "This incident has been resolved.",
102
  "first_seen": "2026-09-04T07:06:16Z",
103
  "impact": "critical",
104
+ "last_seen": "2026-09-04T14:19:03Z",
105
  "resolved_at": "2026-08-05T10:53:09.201-04:00",
106
  "resolved_inferred": false,
107
  "started_at": "2026-08-05T10:44:01.472-04:00",
 
114
  "body": "This incident has been resolved.",
115
  "first_seen": "2026-09-04T07:06:16Z",
116
  "impact": "minor",
117
+ "last_seen": "2026-09-04T14:19:03Z",
118
  "resolved_at": "2026-08-06T12:46:06.425-04:00",
119
  "resolved_inferred": false,
120
  "started_at": "2026-08-04T17:26:47.919-04:00",
 
127
  "body": "This incident has been resolved.",
128
  "first_seen": "2026-09-04T07:06:16Z",
129
  "impact": "minor",
130
+ "last_seen": "2026-09-04T14:19:03Z",
131
  "resolved_at": "2026-07-30T13:10:30.239-04:00",
132
  "resolved_inferred": false,
133
  "started_at": "2026-07-30T12:11:31.229-04:00",
 
140
  "body": "All device scans have caught up and are up to date.",
141
  "first_seen": "2026-09-04T07:06:16Z",
142
  "impact": "minor",
143
+ "last_seen": "2026-09-04T14:19:03Z",
144
  "resolved_at": "2026-07-28T23:34:34.949-04:00",
145
  "resolved_inferred": false,
146
  "started_at": "2026-07-28T10:11:29.951-04:00",
 
153
  "body": "This incident has been resolved.",
154
  "first_seen": "2026-09-04T07:06:16Z",
155
  "impact": "minor",
156
+ "last_seen": "2026-09-04T14:19:03Z",
157
  "resolved_at": "2026-07-27T19:45:18.836-04:00",
158
  "resolved_inferred": false,
159
  "started_at": "2026-07-27T18:15:42.632-04:00",
 
166
  "body": "Users were unable to sign up for new trial accounts through the homepage.",
167
  "first_seen": "2026-09-04T07:06:16Z",
168
  "impact": "none",
169
+ "last_seen": "2026-09-04T14:19:03Z",
170
  "resolved_at": "2026-07-27T10:41:00.000-04:00",
171
  "resolved_inferred": false,
172
  "started_at": "2026-07-27T10:41:00.000-04:00",
 
179
  "body": "This incident has been resolved.",
180
  "first_seen": "2026-09-04T07:06:16Z",
181
  "impact": "minor",
182
+ "last_seen": "2026-09-04T14:19:03Z",
183
  "resolved_at": "2026-07-23T22:36:08.371-04:00",
184
  "resolved_inferred": false,
185
  "started_at": "2026-07-23T17:54:23.365-04:00",
 
192
  "body": "This incident has been resolved.",
193
  "first_seen": "2026-09-04T07:06:16Z",
194
  "impact": "minor",
195
+ "last_seen": "2026-09-04T14:19:03Z",
196
  "resolved_at": "2026-07-20T17:30:35.095-04:00",
197
  "resolved_inferred": false,
198
  "started_at": "2026-07-20T10:47:04.432-04:00",
 
205
  "body": "This incident has been resolved.",
206
  "first_seen": "2026-09-04T07:06:16Z",
207
  "impact": "minor",
208
+ "last_seen": "2026-09-04T14:19:03Z",
209
  "resolved_at": "2026-07-15T19:15:40.875-04:00",
210
  "resolved_inferred": false,
211
  "started_at": "2026-07-14T16:21:56.877-04:00",
 
218
  "body": "This incident has been resolved.",
219
  "first_seen": "2026-09-04T07:06:16Z",
220
  "impact": "minor",
221
+ "last_seen": "2026-09-04T14:19:03Z",
222
  "resolved_at": "2026-06-17T10:06:02.545-04:00",
223
  "resolved_inferred": false,
224
  "started_at": "2026-06-17T09:33:16.822-04:00",
 
231
  "body": "This incident has been resolved.",
232
  "first_seen": "2026-09-04T07:06:16Z",
233
  "impact": "major",
234
+ "last_seen": "2026-09-04T14:19:03Z",
235
  "resolved_at": "2026-06-11T22:02:49.804-04:00",
236
  "resolved_inferred": false,
237
  "started_at": "2026-06-11T19:54:54.099-04:00",
 
244
  "body": "This incident is resolved scans are working as expected now.",
245
  "first_seen": "2026-09-04T07:06:16Z",
246
  "impact": "major",
247
+ "last_seen": "2026-09-04T14:19:03Z",
248
  "resolved_at": "2026-06-10T20:20:33.085-04:00",
249
  "resolved_inferred": false,
250
  "started_at": "2026-06-10T17:50:20.923-04:00",
 
257
  "body": "Connect was temporarily unavailable from about ~2:50 PM MDT to ~3:06 PM MDT",
258
  "first_seen": "2026-09-04T07:06:16Z",
259
  "impact": "none",
260
+ "last_seen": "2026-09-04T14:19:03Z",
261
  "resolved_at": "2026-06-03T17:41:17.551-04:00",
262
  "resolved_inferred": false,
263
  "started_at": "2026-06-03T17:41:17.516-04:00",
 
270
  "body": "This incident has been resolved.",
271
  "first_seen": "2026-09-04T07:06:16Z",
272
  "impact": "minor",
273
+ "last_seen": "2026-09-04T14:19:03Z",
274
  "resolved_at": "2026-06-02T18:55:39.071-04:00",
275
  "resolved_inferred": false,
276
  "started_at": "2026-06-02T15:35:22.000-04:00",
 
283
  "body": "This incident has been resolved.",
284
  "first_seen": "2026-09-04T07:06:16Z",
285
  "impact": "minor",
286
+ "last_seen": "2026-09-04T14:19:03Z",
287
  "resolved_at": "2026-05-11T13:53:56.880-04:00",
288
  "resolved_inferred": false,
289
  "started_at": "2026-05-11T10:23:39.450-04:00",
 
296
  "body": "This incident has been resolved.",
297
  "first_seen": "2026-09-04T07:06:16Z",
298
  "impact": "minor",
299
+ "last_seen": "2026-09-04T14:19:03Z",
300
  "resolved_at": "2026-05-07T13:01:04.775-04:00",
301
  "resolved_inferred": false,
302
  "started_at": "2026-05-07T10:59:05.120-04:00",
 
309
  "body": "This incident has been resolved.",
310
  "first_seen": "2026-09-04T07:06:16Z",
311
  "impact": "critical",
312
+ "last_seen": "2026-09-04T14:19:03Z",
313
  "resolved_at": "2026-04-18T00:07:38.226-04:00",
314
  "resolved_inferred": false,
315
  "started_at": "2026-04-16T23:48:37.284-04:00",
 
322
  "body": "This incident has been resolved.",
323
  "first_seen": "2026-09-04T07:06:16Z",
324
  "impact": "critical",
325
+ "last_seen": "2026-09-04T14:19:03Z",
326
  "resolved_at": "2026-04-16T14:18:43.570-04:00",
327
  "resolved_inferred": false,
328
  "started_at": "2026-04-16T12:59:58.063-04:00",
 
335
  "body": "All delays have now caught up and group counts are up to date.",
336
  "first_seen": "2026-09-04T07:06:16Z",
337
  "impact": "minor",
338
+ "last_seen": "2026-09-04T14:19:03Z",
339
  "resolved_at": "2026-04-09T17:00:10.659-04:00",
340
  "resolved_inferred": false,
341
  "started_at": "2026-04-09T13:02:35.747-04:00",
 
348
  "body": "This incident has been resolved.",
349
  "first_seen": "2026-09-04T07:06:16Z",
350
  "impact": "major",
351
+ "last_seen": "2026-09-04T14:19:03Z",
352
  "resolved_at": "2026-03-31T13:16:43.301-04:00",
353
  "resolved_inferred": false,
354
  "started_at": "2026-03-31T12:23:41.955-04:00",
 
361
  "body": "This incident has been resolved.",
362
  "first_seen": "2026-09-04T07:06:16Z",
363
  "impact": "critical",
364
+ "last_seen": "2026-09-04T14:19:03Z",
365
  "resolved_at": "2026-03-26T16:58:22.293-04:00",
366
  "resolved_inferred": false,
367
  "started_at": "2026-03-26T16:30:29.000-04:00",
 
374
  "body": "This incident has been resolved.",
375
  "first_seen": "2026-09-04T07:06:16Z",
376
  "impact": "minor",
377
+ "last_seen": "2026-09-04T14:19:03Z",
378
  "resolved_at": "2026-03-25T02:21:08.694-04:00",
379
  "resolved_inferred": false,
380
  "started_at": "2026-03-24T12:47:25.264-04:00",
 
387
  "body": "This incident has been resolved.",
388
  "first_seen": "2026-09-04T07:06:16Z",
389
  "impact": "minor",
390
+ "last_seen": "2026-09-04T14:19:03Z",
391
  "resolved_at": "2026-03-16T16:02:58.989-04:00",
392
  "resolved_inferred": false,
393
  "started_at": "2026-03-16T09:54:24.894-04:00",
 
400
  "body": "This incident has been resolved.",
401
  "first_seen": "2026-09-04T07:06:16Z",
402
  "impact": "minor",
403
+ "last_seen": "2026-09-04T14:19:03Z",
404
  "resolved_at": "2026-03-13T17:57:56.555-04:00",
405
  "resolved_inferred": false,
406
  "started_at": "2026-03-13T17:09:55.263-04:00",
 
413
  "body": "This incident has been resolved.",
414
  "first_seen": "2026-09-04T07:06:16Z",
415
  "impact": "minor",
416
+ "last_seen": "2026-09-04T14:19:03Z",
417
  "resolved_at": "2026-03-13T15:35:04.538-04:00",
418
  "resolved_inferred": false,
419
  "started_at": "2026-03-13T13:25:05.911-04:00",
 
426
  "body": "This incident has been resolved.",
427
  "first_seen": "2026-09-04T07:06:16Z",
428
  "impact": "critical",
429
+ "last_seen": "2026-09-04T14:19:03Z",
430
  "resolved_at": "2026-03-12T16:51:05.989-04:00",
431
  "resolved_inferred": false,
432
  "started_at": "2026-03-12T12:30:08.000-04:00",
 
439
  "body": "This incident has been resolved.",
440
  "first_seen": "2026-09-04T07:06:16Z",
441
  "impact": "minor",
442
+ "last_seen": "2026-09-04T14:19:03Z",
443
  "resolved_at": "2026-03-11T12:28:18.984-04:00",
444
  "resolved_inferred": false,
445
  "started_at": "2026-03-11T10:56:04.122-04:00",
 
452
  "body": "We have resolved an issue with our metrics. This incident should have displayed no impact to customers.",
453
  "first_seen": "2026-09-04T07:06:16Z",
454
  "impact": "none",
455
+ "last_seen": "2026-09-04T14:19:03Z",
456
  "resolved_at": "2026-03-07T14:04:21.454-05:00",
457
  "resolved_inferred": false,
458
  "started_at": "2026-03-07T13:31:43.564-05:00",
 
465
  "body": "This incident has been resolved.",
466
  "first_seen": "2026-09-04T07:06:16Z",
467
  "impact": "none",
468
+ "last_seen": "2026-09-04T14:19:03Z",
469
  "resolved_at": "2026-02-20T00:53:12.367-05:00",
470
  "resolved_inferred": false,
471
  "started_at": "2026-02-19T23:35:53.984-05:00",
 
478
  "body": "This incident has been resolved.",
479
  "first_seen": "2026-09-04T07:06:16Z",
480
  "impact": "minor",
481
+ "last_seen": "2026-09-04T14:19:03Z",
482
  "resolved_at": "2026-02-19T14:09:31.623-05:00",
483
  "resolved_inferred": false,
484
  "started_at": "2026-02-19T11:02:33.308-05:00",
 
491
  "body": "This incident has been resolved.",
492
  "first_seen": "2026-09-04T07:06:16Z",
493
  "impact": "minor",
494
+ "last_seen": "2026-09-04T14:19:03Z",
495
  "resolved_at": "2026-02-16T18:11:39.877-05:00",
496
  "resolved_inferred": false,
497
  "started_at": "2026-02-16T16:39:33.988-05:00",
 
504
  "body": "Queues have all caught up and deployments are operational.",
505
  "first_seen": "2026-09-04T07:06:16Z",
506
  "impact": "minor",
507
+ "last_seen": "2026-09-04T14:19:03Z",
508
  "resolved_at": "2026-02-12T14:05:44.209-05:00",
509
  "resolved_inferred": false,
510
  "started_at": "2026-02-12T12:02:20.263-05:00",
 
517
  "body": "Authentication remains stable and we're confident in resolving the issue at this time.",
518
  "first_seen": "2026-09-04T07:06:16Z",
519
  "impact": "critical",
520
+ "last_seen": "2026-09-04T14:19:03Z",
521
  "resolved_at": "2026-02-12T10:08:05.488-05:00",
522
  "resolved_inferred": false,
523
  "started_at": "2026-02-11T09:37:49.603-05:00",
 
530
  "body": "This incident has been resolved.",
531
  "first_seen": "2026-09-04T07:06:16Z",
532
  "impact": "major",
533
+ "last_seen": "2026-09-04T14:19:03Z",
534
  "resolved_at": "2026-01-28T14:27:55.750-05:00",
535
  "resolved_inferred": false,
536
  "started_at": "2026-01-27T15:29:00.208-05:00",
 
543
  "body": "Our email provider is reporting that the incident is fully resolved.",
544
  "first_seen": "2026-09-04T07:06:16Z",
545
  "impact": "minor",
546
+ "last_seen": "2026-09-04T14:19:03Z",
547
  "resolved_at": "2026-02-02T10:40:41.941-05:00",
548
  "resolved_inferred": false,
549
  "started_at": "2026-01-23T11:06:29.559-05:00",
 
556
  "body": "We've determined that deployments are indeed running and that this is a UI bug. We're going to address this issue during normal business hours on Monday.",
557
  "first_seen": "2026-09-04T07:06:16Z",
558
  "impact": "minor",
559
+ "last_seen": "2026-09-04T14:19:03Z",
560
  "resolved_at": "2026-01-23T11:10:48.748-05:00",
561
  "resolved_inferred": false,
562
  "started_at": "2026-01-23T10:27:25.505-05:00",
 
569
  "body": "Microsoft reports that this issue has been resolved.",
570
  "first_seen": "2026-09-04T07:06:16Z",
571
  "impact": "major",
572
+ "last_seen": "2026-09-04T14:19:03Z",
573
  "resolved_at": "2026-01-23T09:06:36.018-05:00",
574
  "resolved_inferred": false,
575
  "started_at": "2026-01-22T16:04:46.000-05:00",
 
582
  "body": "This incident has been resolved.",
583
  "first_seen": "2026-09-04T07:06:16Z",
584
  "impact": "minor",
585
+ "last_seen": "2026-09-04T14:19:03Z",
586
  "resolved_at": "2026-01-21T12:53:29.014-05:00",
587
  "resolved_inferred": false,
588
  "started_at": "2026-01-21T10:27:39.303-05:00",
 
595
  "body": "This incident has been resolved.",
596
  "first_seen": "2026-09-04T07:06:16Z",
597
  "impact": "critical",
598
+ "last_seen": "2026-09-04T14:19:03Z",
599
  "resolved_at": "2026-01-20T16:27:42.914-05:00",
600
  "resolved_inferred": false,
601
  "started_at": "2026-01-20T09:20:28.265-05:00",
 
608
  "body": "This incident has been resolved.",
609
  "first_seen": "2026-09-04T07:06:16Z",
610
  "impact": "minor",
611
+ "last_seen": "2026-09-04T14:19:03Z",
612
  "resolved_at": "2026-01-14T15:04:26.727-05:00",
613
  "resolved_inferred": false,
614
  "started_at": "2026-01-14T10:55:26.211-05:00",
 
621
  "body": "This incident has been resolved.",
622
  "first_seen": "2026-09-04T07:06:16Z",
623
  "impact": "minor",
624
+ "last_seen": "2026-09-04T14:19:03Z",
625
  "resolved_at": "2026-01-13T14:08:08.965-05:00",
626
  "resolved_inferred": false,
627
  "started_at": "2026-01-13T11:30:26.000-05:00",
 
634
  "body": "This incident has been resolved.",
635
  "first_seen": "2026-09-04T07:06:16Z",
636
  "impact": "minor",
637
+ "last_seen": "2026-09-04T14:19:03Z",
638
  "resolved_at": "2026-01-12T18:10:18.408-05:00",
639
  "resolved_inferred": false,
640
  "started_at": "2026-01-12T10:12:43.771-05:00",
 
647
  "body": "After monitoring we are not seeing any more delays",
648
  "first_seen": "2026-09-04T07:06:16Z",
649
  "impact": "minor",
650
+ "last_seen": "2026-09-04T14:19:03Z",
651
  "resolved_at": "2025-12-15T17:04:36.331-05:00",
652
  "resolved_inferred": false,
653
  "started_at": "2025-12-15T13:19:04.406-05:00",
api/v/pendo.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "pendo",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pendo.io",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "We have investigated the issue and consider this incident resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-09-02T12:45:05.756-04:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-02T11:48:42.594-04:00",
@@ -25,7 +25,7 @@
25
  "body": "This incident is resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-07-27T11:25:00.916-04:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-07-27T10:48:04.520-04:00",
@@ -38,7 +38,7 @@
38
  "body": "This disruption has been fully resolved. The Stable Web SDK was not impacted at any point. Thank you for your patience.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "none",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-07-14T11:53:17.446-04:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-07-14T08:25:53.000-04:00",
@@ -51,7 +51,7 @@
51
  "body": "All event processing delays have been caught up. This incident is resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-07-10T08:35:09.764-04:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-07-10T03:30:07.000-04:00",
@@ -64,7 +64,7 @@
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "major",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-07-03T09:08:31.100-04:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-07-02T11:47:10.000-04:00",
@@ -77,7 +77,7 @@
77
  "body": "Between June 3, 2026 and June 4, 2026, some customers experienced two related issues affecting in-app guides on the Pendo platform (pendo.io environment):\n\nGuide Targeting Disruption: Guides that used negated, nested segment rules (\"Segment is not equal to...\") were incorrectly evaluated due to a segment flag processing bug. Affected guides may have failed to display to intended audiences during this window.\n\nConversational AI Guide Editor Unavailable: The Conversational AI interface within the guide editor (\"Edit in Pendo\") was inaccessible.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "none",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-06-04T13:00:20.000-04:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-06-04T13:00:20.000-04:00",
@@ -90,7 +90,7 @@
90
  "body": "This incident has been resolved and Pendo Academy should be accessible across all regions now.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "critical",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-05-29T11:32:22.193-04:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-05-29T08:40:28.092-04:00",
@@ -103,7 +103,7 @@
103
  "body": "This issue is now formally resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-05-28T20:16:14.945-04:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-05-28T17:34:27.558-04:00",
@@ -116,7 +116,7 @@
116
  "body": "This incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-05-29T16:00:38.000-04:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-05-28T10:41:27.854-04:00",
@@ -129,7 +129,7 @@
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-05-27T19:33:57.759-04:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-05-27T11:56:38.924-04:00",
@@ -142,7 +142,7 @@
142
  "body": "This incident has now been fully resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "critical",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2026-05-19T15:06:43.091-04:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-05-19T12:50:18.416-04:00",
@@ -155,7 +155,7 @@
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "minor",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2026-05-22T01:00:16.000-04:00",
160
  "resolved_inferred": false,
161
  "started_at": "2026-05-19T06:24:13.000-04:00",
@@ -168,7 +168,7 @@
168
  "body": "We consider this issue fully resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "minor",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2026-05-13T18:21:35.831-04:00",
173
  "resolved_inferred": false,
174
  "started_at": "2026-05-13T09:29:15.000-04:00",
@@ -181,7 +181,7 @@
181
  "body": "The rollback we have implemented has successfully fixed the \"invalid scope\" authentication error and this issue is now resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "minor",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2026-05-08T15:09:07.520-04:00",
186
  "resolved_inferred": false,
187
  "started_at": "2026-05-08T13:05:11.971-04:00",
@@ -194,7 +194,7 @@
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2026-04-14T02:39:58.521-04:00",
199
  "resolved_inferred": false,
200
  "started_at": "2026-04-13T17:31:54.224-04:00",
@@ -207,7 +207,7 @@
207
  "body": "We are happy to report that the issue preventing users in our US region from editing existing segments has been fully resolved. All systems are now operating normally, and you can once again edit and manage all of your segments without error.\n\nWe apologize for the disruption this may have caused and appreciate your patience as we worked to implement a fix.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "minor",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2026-03-18T09:05:19.818-04:00",
212
  "resolved_inferred": false,
213
  "started_at": "2026-03-18T08:50:11.802-04:00",
@@ -220,7 +220,7 @@
220
  "body": "Following testing, we have deployed a fix and email information is now appearing as expected and we consider the issue resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2026-03-12T14:07:07.333-04:00",
225
  "resolved_inferred": false,
226
  "started_at": "2026-03-12T10:49:44.014-04:00",
@@ -233,7 +233,7 @@
233
  "body": "After monitoring guide and resource center behavior and conducting a review of all guide statuses, we consider this issue fully resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2026-02-08T09:57:41.855-05:00",
238
  "resolved_inferred": false,
239
  "started_at": "2026-02-05T07:21:24.578-05:00",
@@ -246,7 +246,7 @@
246
  "body": "Guide functionality and deliverability have been fully restored. All guides that were temporarily moved to a Draft state have now been returned to their previous status.\n\nWe believe Resource Center Guide Modules were not impacted in Production or Staging environments. An issue impacting the ability to edit some guides within RC Guide Modules while in Draft state was identified and is being addressed separately.\n\nSome guides may appear to still be in a Draft state due to browser caching. Logging out and back into Pendo will refresh the UI and reflect the correct guide status.\n\nThis incident is now resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "critical",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2026-02-04T23:45:52.245-05:00",
251
  "resolved_inferred": false,
252
  "started_at": "2026-02-04T16:48:53.519-05:00",
@@ -259,7 +259,7 @@
259
  "body": "The latency issue with our Support Bot vendor has been resolved. The Support Bot is now operating normally. Thank you for your patience while this was investigated.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "major",
262
- "last_seen": "2026-09-04T12:24:18Z",
263
  "resolved_at": "2026-01-09T16:18:19.528-05:00",
264
  "resolved_inferred": false,
265
  "started_at": "2026-01-09T15:46:49.575-05:00",
@@ -272,7 +272,7 @@
272
  "body": "This incident has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "none",
275
- "last_seen": "2026-09-04T12:24:18Z",
276
  "resolved_at": "2025-11-25T08:33:34.375-05:00",
277
  "resolved_inferred": false,
278
  "started_at": "2025-11-20T10:48:13.000-05:00",
@@ -285,7 +285,7 @@
285
  "body": "This issue has been fully resolved.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "minor",
288
- "last_seen": "2026-09-04T12:24:18Z",
289
  "resolved_at": "2025-10-07T14:07:28.602-04:00",
290
  "resolved_inferred": false,
291
  "started_at": "2025-10-07T10:10:04.299-04:00",
 
3
  "slug": "pendo",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pendo.io",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "We have investigated the issue and consider this incident resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-09-02T12:45:05.756-04:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-02T11:48:42.594-04:00",
 
25
  "body": "This incident is resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-07-27T11:25:00.916-04:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-07-27T10:48:04.520-04:00",
 
38
  "body": "This disruption has been fully resolved. The Stable Web SDK was not impacted at any point. Thank you for your patience.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "none",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-07-14T11:53:17.446-04:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-07-14T08:25:53.000-04:00",
 
51
  "body": "All event processing delays have been caught up. This incident is resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-07-10T08:35:09.764-04:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-07-10T03:30:07.000-04:00",
 
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "major",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-07-03T09:08:31.100-04:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-07-02T11:47:10.000-04:00",
 
77
  "body": "Between June 3, 2026 and June 4, 2026, some customers experienced two related issues affecting in-app guides on the Pendo platform (pendo.io environment):\n\nGuide Targeting Disruption: Guides that used negated, nested segment rules (\"Segment is not equal to...\") were incorrectly evaluated due to a segment flag processing bug. Affected guides may have failed to display to intended audiences during this window.\n\nConversational AI Guide Editor Unavailable: The Conversational AI interface within the guide editor (\"Edit in Pendo\") was inaccessible.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "none",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-06-04T13:00:20.000-04:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-06-04T13:00:20.000-04:00",
 
90
  "body": "This incident has been resolved and Pendo Academy should be accessible across all regions now.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "critical",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-05-29T11:32:22.193-04:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-05-29T08:40:28.092-04:00",
 
103
  "body": "This issue is now formally resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-05-28T20:16:14.945-04:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-05-28T17:34:27.558-04:00",
 
116
  "body": "This incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-05-29T16:00:38.000-04:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-05-28T10:41:27.854-04:00",
 
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-05-27T19:33:57.759-04:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-05-27T11:56:38.924-04:00",
 
142
  "body": "This incident has now been fully resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "critical",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2026-05-19T15:06:43.091-04:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-05-19T12:50:18.416-04:00",
 
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "minor",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2026-05-22T01:00:16.000-04:00",
160
  "resolved_inferred": false,
161
  "started_at": "2026-05-19T06:24:13.000-04:00",
 
168
  "body": "We consider this issue fully resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "minor",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2026-05-13T18:21:35.831-04:00",
173
  "resolved_inferred": false,
174
  "started_at": "2026-05-13T09:29:15.000-04:00",
 
181
  "body": "The rollback we have implemented has successfully fixed the \"invalid scope\" authentication error and this issue is now resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "minor",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2026-05-08T15:09:07.520-04:00",
186
  "resolved_inferred": false,
187
  "started_at": "2026-05-08T13:05:11.971-04:00",
 
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2026-04-14T02:39:58.521-04:00",
199
  "resolved_inferred": false,
200
  "started_at": "2026-04-13T17:31:54.224-04:00",
 
207
  "body": "We are happy to report that the issue preventing users in our US region from editing existing segments has been fully resolved. All systems are now operating normally, and you can once again edit and manage all of your segments without error.\n\nWe apologize for the disruption this may have caused and appreciate your patience as we worked to implement a fix.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "minor",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2026-03-18T09:05:19.818-04:00",
212
  "resolved_inferred": false,
213
  "started_at": "2026-03-18T08:50:11.802-04:00",
 
220
  "body": "Following testing, we have deployed a fix and email information is now appearing as expected and we consider the issue resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2026-03-12T14:07:07.333-04:00",
225
  "resolved_inferred": false,
226
  "started_at": "2026-03-12T10:49:44.014-04:00",
 
233
  "body": "After monitoring guide and resource center behavior and conducting a review of all guide statuses, we consider this issue fully resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2026-02-08T09:57:41.855-05:00",
238
  "resolved_inferred": false,
239
  "started_at": "2026-02-05T07:21:24.578-05:00",
 
246
  "body": "Guide functionality and deliverability have been fully restored. All guides that were temporarily moved to a Draft state have now been returned to their previous status.\n\nWe believe Resource Center Guide Modules were not impacted in Production or Staging environments. An issue impacting the ability to edit some guides within RC Guide Modules while in Draft state was identified and is being addressed separately.\n\nSome guides may appear to still be in a Draft state due to browser caching. Logging out and back into Pendo will refresh the UI and reflect the correct guide status.\n\nThis incident is now resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "critical",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2026-02-04T23:45:52.245-05:00",
251
  "resolved_inferred": false,
252
  "started_at": "2026-02-04T16:48:53.519-05:00",
 
259
  "body": "The latency issue with our Support Bot vendor has been resolved. The Support Bot is now operating normally. Thank you for your patience while this was investigated.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "major",
262
+ "last_seen": "2026-09-04T14:19:03Z",
263
  "resolved_at": "2026-01-09T16:18:19.528-05:00",
264
  "resolved_inferred": false,
265
  "started_at": "2026-01-09T15:46:49.575-05:00",
 
272
  "body": "This incident has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "none",
275
+ "last_seen": "2026-09-04T14:19:03Z",
276
  "resolved_at": "2025-11-25T08:33:34.375-05:00",
277
  "resolved_inferred": false,
278
  "started_at": "2025-11-20T10:48:13.000-05:00",
 
285
  "body": "This issue has been fully resolved.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "minor",
288
+ "last_seen": "2026-09-04T14:19:03Z",
289
  "resolved_at": "2025-10-07T14:07:28.602-04:00",
290
  "resolved_inferred": false,
291
  "started_at": "2025-10-07T10:10:04.299-04:00",
api/v/percy.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "percy",
4
  "platform": "statuspage",
5
  "status_url": "https://status.percy.io",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "Percy builds were degraded for ~50 mins [7.30 AM PDT to 8.20 AM PDT on 13th July] due to an existing Google Cloud Provider incident\nWe have moved our infrastructure from the impacted GCP node pool and are back to normal processing\n\nGCP incident details - https://console.cloud.google.com/servicehealth/incidentDetails/projects%2Fpercy-prod%2Flocations%2Fglobal%2Fevents%2FZBYNZVS?project=percy-prod&tab=full-history",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-07-12T19:00:00.000-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-07-12T19:00:00.000-07:00",
@@ -25,7 +25,7 @@
25
  "body": "Percy customers were facing intermittent login issues from 7:45 pm PDT to 10:14 PM PDT on 6th July\nWe have identified the issue and login functionality has been fully restored",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-07-06T07:30:00.000-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-07-06T07:30:00.000-07:00",
@@ -38,7 +38,7 @@
38
  "body": "A subset of Percy builds experienced slowness from 4:15 PM PDT to 5 PM PDT [29th June]\nThe issue is identified and resolved, services are operating normally",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-06-29T04:30:00.000-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-06-29T04:30:00.000-07:00",
@@ -51,7 +51,7 @@
51
  "body": "In the 20 mins duration some customers might have seen some missing snapshots in the build or failures in creating builds themselves with the 401 status code on the Percy CLI logs.\n\nWe have fixed the issue and monitoring the stack.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-05-29T04:30:00.000-07:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-05-29T04:30:00.000-07:00",
@@ -64,7 +64,7 @@
64
  "body": "Percy experienced login failures for a subset of users between 11:54 PM PDT (18 May) \u2013 12:54 AM PDT (19 May)\nWe have identified the issue and login functionality has been fully restored",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "none",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-05-18T11:00:00.000-07:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-05-18T11:00:00.000-07:00",
@@ -77,7 +77,7 @@
77
  "body": "Between 4:30 AM and 9:30 AM PDT on May 11, 2026, some Percy builds took longer than usual to complete due to increased database contention. Builds were not lost - only delayed. The issue has been mitigated and processing times are back to normal. We're investigating the root cause to prevent recurrence in future.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-05-11T04:30:00.000-07:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-05-11T04:30:00.000-07:00",
@@ -90,7 +90,7 @@
90
  "body": "Customers using Percy on Automate experienced build failures between May 5th, 8:00 AM PDT and May 6th, 1:30 AM PDT.\nThe issue has now been resolved, and Percy on Automate builds should be functioning as expected",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-05-05T08:00:00.000-07:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-05-04T19:30:00.000-07:00",
@@ -103,7 +103,7 @@
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-04-15T11:31:50.340-07:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-04-15T09:39:00.000-07:00",
@@ -116,7 +116,7 @@
116
  "body": "Some users might have faced issue while logging in during ~35 min window. No existing sessions were impacted.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-03-25T06:30:00.000-07:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-03-24T18:30:00.000-07:00",
@@ -129,7 +129,7 @@
129
  "body": "- Between February 8, 2026 (10:30 AM \u2013 2:30 PM UTC) and February 9, 2026 (12:00 PM \u2013 1:30 PM UTC) some customers may have noticed incorrect visual diffs on Percy (Safari on iPhone)\n- The issue occurred due to an incorrect screenshot capture where a \u201cconnection not private\u201d error page was rendered instead of the expected page\n- The impact was limited, affecting a very small percentage of builds across a small number of organisations\n- Our engineering team has identified and addressed the underlying issue \n- All Percy services are now operating normally\nWe sincerely apologise for any confusion or inconvenience this may have caused",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "none",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-02-07T13:00:00.000-08:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-02-07T13:00:00.000-08:00",
@@ -142,7 +142,7 @@
142
  "body": "Marking this as resolved as original incidence from Cloudflare is marked as resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "major",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2026-01-27T20:49:51.858-08:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-01-27T12:00:31.000-08:00",
@@ -155,7 +155,7 @@
155
  "body": "A subset of users were impacted by infinite reloads and unable to access percy dashboard while attempting to access a build URL on percy dashboard - which internally attempted sign in with browserstack.com. The issue is fixed as of 5:30 AM PST and all dashboard access should be working as expected now.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "minor",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2026-01-09T02:00:00.000-08:00",
160
  "resolved_inferred": false,
161
  "started_at": "2026-01-09T02:00:00.000-08:00",
@@ -168,7 +168,7 @@
168
  "body": "We have resumed normal operations and cleared up Percy backlog of builds. Build processing speed is back to normalcy",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "critical",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2025-11-18T11:17:15.423-08:00",
173
  "resolved_inferred": false,
174
  "started_at": "2025-11-18T03:55:03.862-08:00",
@@ -181,7 +181,7 @@
181
  "body": "We are currently experiencing degradation in visual difference impacting Percy builds due to an underlying Cloudflare issue. Affected builds may show snapshots with blank pages or missing assets, which can result in incorrect Visual differences\nWindow : 10:30 PM PDT 22nd Oct - 1.47 AM PDT 23rd Oct",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "none",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2025-10-22T10:00:00.000-07:00",
186
  "resolved_inferred": false,
187
  "started_at": "2025-10-22T10:00:00.000-07:00",
@@ -194,7 +194,7 @@
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2025-10-20T12:45:35.000-07:00",
199
  "resolved_inferred": false,
200
  "started_at": "2025-10-20T10:37:45.172-07:00",
@@ -207,7 +207,7 @@
207
  "body": "We are currently observing degraded performance from 6.30 AM - 7.45 AM PDT in Percy, primarily affecting build processing times and dashboard responsiveness. Our investigation indicates that this is due to an ongoing AWS US-East-1 regional outage impacting one of our critical third-party services - LaunchDarkly - which we use for configuration management and feature flag delivery. We are actively monitoring the situation and working with teams to mitigate impact. Builds may take longer to start or complete until the upstream issue is resolved.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "major",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2025-10-20T06:30:07.000-07:00",
212
  "resolved_inferred": false,
213
  "started_at": "2025-10-20T06:30:07.000-07:00",
@@ -220,7 +220,7 @@
220
  "body": "We are currently observing degraded performance from 12:20 PM PDT to 1 PM PDT [20th October] in Percy, primarily affecting build processing times and dashboard responsiveness. Our investigation indicates that this is due to an ongoing AWS US-East-1 regional outage impacting one of our critical third-party services . We are actively monitoring the situation and working with teams to mitigate impact. Builds may take longer to start or complete until the upstream issue is resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "major",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2025-10-20T13:00:00.000-07:00",
225
  "resolved_inferred": false,
226
  "started_at": "2025-10-20T00:00:00.000-07:00",
@@ -233,7 +233,7 @@
233
  "body": "On October 14th from 1.30 PM PDT to 8.30 PM PDT (14th October), Percy web experienced a slowness in processing of builds in majority of organisations. This was due to an underlying infrastructure degradation. Our team deployed a fix to address slow build times. All systems are now operating normally. We sincerely apologise for any disruption this may have caused.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "none",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2025-10-14T01:00:00.000-07:00",
238
  "resolved_inferred": false,
239
  "started_at": "2025-10-14T01:00:00.000-07:00",
@@ -246,7 +246,7 @@
246
  "body": "[Minor impact on build performance] On September 9th , our team deployed a fix to address the slow build times experienced by some organisations. This was due to an underlying infrastructure degradation. All systems are now operating normally. We sincerely apologise for any disruption this may have caused.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "minor",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2025-09-09T20:45:00.000-07:00",
251
  "resolved_inferred": false,
252
  "started_at": "2025-09-09T03:00:00.000-07:00",
 
3
  "slug": "percy",
4
  "platform": "statuspage",
5
  "status_url": "https://status.percy.io",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "Percy builds were degraded for ~50 mins [7.30 AM PDT to 8.20 AM PDT on 13th July] due to an existing Google Cloud Provider incident\nWe have moved our infrastructure from the impacted GCP node pool and are back to normal processing\n\nGCP incident details - https://console.cloud.google.com/servicehealth/incidentDetails/projects%2Fpercy-prod%2Flocations%2Fglobal%2Fevents%2FZBYNZVS?project=percy-prod&tab=full-history",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-07-12T19:00:00.000-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-07-12T19:00:00.000-07:00",
 
25
  "body": "Percy customers were facing intermittent login issues from 7:45 pm PDT to 10:14 PM PDT on 6th July\nWe have identified the issue and login functionality has been fully restored",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-07-06T07:30:00.000-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-07-06T07:30:00.000-07:00",
 
38
  "body": "A subset of Percy builds experienced slowness from 4:15 PM PDT to 5 PM PDT [29th June]\nThe issue is identified and resolved, services are operating normally",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-06-29T04:30:00.000-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-06-29T04:30:00.000-07:00",
 
51
  "body": "In the 20 mins duration some customers might have seen some missing snapshots in the build or failures in creating builds themselves with the 401 status code on the Percy CLI logs.\n\nWe have fixed the issue and monitoring the stack.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-05-29T04:30:00.000-07:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-05-29T04:30:00.000-07:00",
 
64
  "body": "Percy experienced login failures for a subset of users between 11:54 PM PDT (18 May) \u2013 12:54 AM PDT (19 May)\nWe have identified the issue and login functionality has been fully restored",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "none",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-05-18T11:00:00.000-07:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-05-18T11:00:00.000-07:00",
 
77
  "body": "Between 4:30 AM and 9:30 AM PDT on May 11, 2026, some Percy builds took longer than usual to complete due to increased database contention. Builds were not lost - only delayed. The issue has been mitigated and processing times are back to normal. We're investigating the root cause to prevent recurrence in future.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-05-11T04:30:00.000-07:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-05-11T04:30:00.000-07:00",
 
90
  "body": "Customers using Percy on Automate experienced build failures between May 5th, 8:00 AM PDT and May 6th, 1:30 AM PDT.\nThe issue has now been resolved, and Percy on Automate builds should be functioning as expected",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-05-05T08:00:00.000-07:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-05-04T19:30:00.000-07:00",
 
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-04-15T11:31:50.340-07:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-04-15T09:39:00.000-07:00",
 
116
  "body": "Some users might have faced issue while logging in during ~35 min window. No existing sessions were impacted.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "minor",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-03-25T06:30:00.000-07:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-03-24T18:30:00.000-07:00",
 
129
  "body": "- Between February 8, 2026 (10:30 AM \u2013 2:30 PM UTC) and February 9, 2026 (12:00 PM \u2013 1:30 PM UTC) some customers may have noticed incorrect visual diffs on Percy (Safari on iPhone)\n- The issue occurred due to an incorrect screenshot capture where a \u201cconnection not private\u201d error page was rendered instead of the expected page\n- The impact was limited, affecting a very small percentage of builds across a small number of organisations\n- Our engineering team has identified and addressed the underlying issue \n- All Percy services are now operating normally\nWe sincerely apologise for any confusion or inconvenience this may have caused",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "none",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-02-07T13:00:00.000-08:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-02-07T13:00:00.000-08:00",
 
142
  "body": "Marking this as resolved as original incidence from Cloudflare is marked as resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "major",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2026-01-27T20:49:51.858-08:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-01-27T12:00:31.000-08:00",
 
155
  "body": "A subset of users were impacted by infinite reloads and unable to access percy dashboard while attempting to access a build URL on percy dashboard - which internally attempted sign in with browserstack.com. The issue is fixed as of 5:30 AM PST and all dashboard access should be working as expected now.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "minor",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2026-01-09T02:00:00.000-08:00",
160
  "resolved_inferred": false,
161
  "started_at": "2026-01-09T02:00:00.000-08:00",
 
168
  "body": "We have resumed normal operations and cleared up Percy backlog of builds. Build processing speed is back to normalcy",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "critical",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2025-11-18T11:17:15.423-08:00",
173
  "resolved_inferred": false,
174
  "started_at": "2025-11-18T03:55:03.862-08:00",
 
181
  "body": "We are currently experiencing degradation in visual difference impacting Percy builds due to an underlying Cloudflare issue. Affected builds may show snapshots with blank pages or missing assets, which can result in incorrect Visual differences\nWindow : 10:30 PM PDT 22nd Oct - 1.47 AM PDT 23rd Oct",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "none",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2025-10-22T10:00:00.000-07:00",
186
  "resolved_inferred": false,
187
  "started_at": "2025-10-22T10:00:00.000-07:00",
 
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2025-10-20T12:45:35.000-07:00",
199
  "resolved_inferred": false,
200
  "started_at": "2025-10-20T10:37:45.172-07:00",
 
207
  "body": "We are currently observing degraded performance from 6.30 AM - 7.45 AM PDT in Percy, primarily affecting build processing times and dashboard responsiveness. Our investigation indicates that this is due to an ongoing AWS US-East-1 regional outage impacting one of our critical third-party services - LaunchDarkly - which we use for configuration management and feature flag delivery. We are actively monitoring the situation and working with teams to mitigate impact. Builds may take longer to start or complete until the upstream issue is resolved.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "major",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2025-10-20T06:30:07.000-07:00",
212
  "resolved_inferred": false,
213
  "started_at": "2025-10-20T06:30:07.000-07:00",
 
220
  "body": "We are currently observing degraded performance from 12:20 PM PDT to 1 PM PDT [20th October] in Percy, primarily affecting build processing times and dashboard responsiveness. Our investigation indicates that this is due to an ongoing AWS US-East-1 regional outage impacting one of our critical third-party services . We are actively monitoring the situation and working with teams to mitigate impact. Builds may take longer to start or complete until the upstream issue is resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "major",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2025-10-20T13:00:00.000-07:00",
225
  "resolved_inferred": false,
226
  "started_at": "2025-10-20T00:00:00.000-07:00",
 
233
  "body": "On October 14th from 1.30 PM PDT to 8.30 PM PDT (14th October), Percy web experienced a slowness in processing of builds in majority of organisations. This was due to an underlying infrastructure degradation. Our team deployed a fix to address slow build times. All systems are now operating normally. We sincerely apologise for any disruption this may have caused.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "none",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2025-10-14T01:00:00.000-07:00",
238
  "resolved_inferred": false,
239
  "started_at": "2025-10-14T01:00:00.000-07:00",
 
246
  "body": "[Minor impact on build performance] On September 9th , our team deployed a fix to address the slow build times experienced by some organisations. This was due to an underlying infrastructure degradation. All systems are now operating normally. We sincerely apologise for any disruption this may have caused.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "minor",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2025-09-09T20:45:00.000-07:00",
251
  "resolved_inferred": false,
252
  "started_at": "2025-09-09T03:00:00.000-07:00",
api/v/perimeter-81.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "perimeter-81",
4
  "platform": "statuspage",
5
  "status_url": "https://status.perimeter81.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
3
  "slug": "perimeter-81",
4
  "platform": "statuspage",
5
  "status_url": "https://status.perimeter81.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
api/v/perimeterx.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "perimeterx",
4
  "platform": "statuspage",
5
  "status_url": "https://status.perimeterx.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
3
  "slug": "perimeterx",
4
  "platform": "statuspage",
5
  "status_url": "https://status.perimeterx.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
api/v/permit-io.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "permit-io",
4
  "platform": "instatus",
5
  "status_url": "https://permit-io.instatus.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": false,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
3
  "slug": "permit-io",
4
  "platform": "instatus",
5
  "status_url": "https://permit-io.instatus.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": false,
9
  "first_watched": "2026-09-04T07:06:16Z",
api/v/phantombuster.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "phantombuster",
4
  "platform": "statuspage",
5
  "status_url": "https://status.phantombuster.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
3
  "slug": "phantombuster",
4
  "platform": "statuspage",
5
  "status_url": "https://status.phantombuster.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
api/v/pinecone.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "pinecone",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pinecone.io",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-09-01T19:40:57.000Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-01T15:04:56.000Z",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-08-25T16:11:48.000Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-25T15:50:32.000Z",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "critical",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-07-21T19:40:02.000Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-07-21T19:10:07.000Z",
@@ -51,7 +51,7 @@
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-07-20T18:00:03.000Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-07-20T16:44:41.000Z",
@@ -64,7 +64,7 @@
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-07-13T04:15:55.000Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-07-12T23:21:10.000Z",
@@ -77,7 +77,7 @@
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-07-09T14:37:36.086Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-07-09T09:50:14.000Z",
@@ -90,7 +90,7 @@
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-06-18T18:23:35.000Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-06-18T10:00:47.000Z",
@@ -103,7 +103,7 @@
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "none",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-06-16T17:05:41.000Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-06-16T13:05:50.000Z",
@@ -116,7 +116,7 @@
116
  "body": "This incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "major",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-06-06T20:40:47.000Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-06-06T17:05:39.000Z",
@@ -129,7 +129,7 @@
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-06-06T15:50:17.000Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-06-06T13:05:24.000Z",
@@ -142,7 +142,7 @@
142
  "body": "This incident has been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "minor",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2026-06-06T01:15:33.000Z",
147
  "resolved_inferred": false,
148
  "started_at": "2026-06-06T00:48:34.000Z",
@@ -155,7 +155,7 @@
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "major",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2026-05-25T15:00:21.000Z",
160
  "resolved_inferred": false,
161
  "started_at": "2026-05-25T13:41:50.000Z",
@@ -168,7 +168,7 @@
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2026-05-13T21:15:40.000Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-05-13T20:14:38.000Z",
@@ -181,7 +181,7 @@
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "major",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2026-05-06T20:30:10.000Z",
186
  "resolved_inferred": false,
187
  "started_at": "2026-05-06T20:02:56.000Z",
@@ -194,7 +194,7 @@
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2026-05-06T15:20:04.000Z",
199
  "resolved_inferred": false,
200
  "started_at": "2026-05-06T15:00:30.000Z",
@@ -207,7 +207,7 @@
207
  "body": "This incident has been resolved.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "major",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2026-03-13T09:53:17.000Z",
212
  "resolved_inferred": false,
213
  "started_at": "2026-03-13T08:50:03.000Z",
@@ -220,7 +220,7 @@
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2026-03-05T23:02:17.000Z",
225
  "resolved_inferred": false,
226
  "started_at": "2026-03-05T21:57:20.000Z",
@@ -233,7 +233,7 @@
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2026-03-04T22:16:28.000Z",
238
  "resolved_inferred": false,
239
  "started_at": "2026-03-04T21:06:09.000Z",
@@ -246,7 +246,7 @@
246
  "body": "This incident has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2026-02-24T01:52:43.000Z",
251
  "resolved_inferred": false,
252
  "started_at": "2026-02-23T23:14:35.000Z",
@@ -259,7 +259,7 @@
259
  "body": "This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "minor",
262
- "last_seen": "2026-09-04T12:24:18Z",
263
  "resolved_at": "2026-02-05T21:57:04.000Z",
264
  "resolved_inferred": false,
265
  "started_at": "2026-02-05T10:55:24.000Z",
@@ -272,7 +272,7 @@
272
  "body": "This incident has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "major",
275
- "last_seen": "2026-09-04T12:24:18Z",
276
  "resolved_at": "2026-01-15T15:30:56.000Z",
277
  "resolved_inferred": false,
278
  "started_at": "2026-01-15T12:12:55.000Z",
@@ -285,7 +285,7 @@
285
  "body": "This incident has been resolved.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "major",
288
- "last_seen": "2026-09-04T12:24:18Z",
289
  "resolved_at": "2026-01-02T17:58:09.483Z",
290
  "resolved_inferred": false,
291
  "started_at": "2026-01-02T16:31:16.954Z",
@@ -298,7 +298,7 @@
298
  "body": "This incident has been resolved.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "major",
301
- "last_seen": "2026-09-04T12:24:18Z",
302
  "resolved_at": "2025-12-31T03:29:18.000Z",
303
  "resolved_inferred": false,
304
  "started_at": "2025-12-31T03:13:07.000Z",
@@ -311,7 +311,7 @@
311
  "body": "From 8:15 PM to 8:50 PM UTC, some users experienced partial control plane unavailability.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "none",
314
- "last_seen": "2026-09-04T12:24:18Z",
315
  "resolved_at": "2025-12-19T01:15:00.000Z",
316
  "resolved_inferred": false,
317
  "started_at": "2025-12-19T01:15:00.000Z",
@@ -324,7 +324,7 @@
324
  "body": "This incident has been resolved.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "major",
327
- "last_seen": "2026-09-04T12:24:18Z",
328
  "resolved_at": "2025-12-15T22:02:32.693Z",
329
  "resolved_inferred": false,
330
  "started_at": "2025-12-15T10:39:51.000Z",
@@ -337,7 +337,7 @@
337
  "body": "This incident has been resolved.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "minor",
340
- "last_seen": "2026-09-04T12:24:18Z",
341
  "resolved_at": "2025-12-10T01:50:19.000Z",
342
  "resolved_inferred": false,
343
  "started_at": "2025-12-09T20:15:00.000Z",
@@ -350,7 +350,7 @@
350
  "body": "From 3:43 PM EST to 3:50 PM EST, some embed and rerank requests were unavailable.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "none",
353
- "last_seen": "2026-09-04T12:24:18Z",
354
  "resolved_at": "2025-12-08T20:43:00.000Z",
355
  "resolved_inferred": false,
356
  "started_at": "2025-12-08T20:43:00.000Z",
@@ -363,7 +363,7 @@
363
  "body": "This incident has been resolved.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "major",
366
- "last_seen": "2026-09-04T12:24:18Z",
367
  "resolved_at": "2025-12-05T20:42:52.000Z",
368
  "resolved_inferred": false,
369
  "started_at": "2025-12-05T18:36:46.000Z",
@@ -376,7 +376,7 @@
376
  "body": "This incident has been resolved.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "major",
379
- "last_seen": "2026-09-04T12:24:18Z",
380
  "resolved_at": "2025-12-03T16:40:17.000Z",
381
  "resolved_inferred": false,
382
  "started_at": "2025-12-03T15:53:51.000Z",
@@ -389,7 +389,7 @@
389
  "body": "This incident has been resolved.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "major",
392
- "last_seen": "2026-09-04T12:24:18Z",
393
  "resolved_at": "2025-11-24T18:30:05.000Z",
394
  "resolved_inferred": false,
395
  "started_at": "2025-11-24T17:28:25.000Z",
@@ -402,7 +402,7 @@
402
  "body": "Index-level usage metrics were unavailable for approximately 24 hours beginning at around 9:00 PM EST on November 12th",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "none",
405
- "last_seen": "2026-09-04T12:24:18Z",
406
  "resolved_at": "2025-11-13T02:00:00.000Z",
407
  "resolved_inferred": false,
408
  "started_at": "2025-11-13T02:00:00.000Z",
@@ -415,7 +415,7 @@
415
  "body": "This incident has been resolved.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "major",
418
- "last_seen": "2026-09-04T12:24:18Z",
419
  "resolved_at": "2025-11-06T14:40:24.000Z",
420
  "resolved_inferred": false,
421
  "started_at": "2025-11-06T14:38:10.000Z",
@@ -428,7 +428,7 @@
428
  "body": "From 4:58 PM EST to 5:10 PM EST, the cohere-rerank-3.5 model experienced partial unavailability.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "none",
431
- "last_seen": "2026-09-04T12:24:18Z",
432
  "resolved_at": "2025-10-30T22:00:04.733Z",
433
  "resolved_inferred": false,
434
  "started_at": "2025-10-30T22:00:04.669Z",
@@ -441,7 +441,7 @@
441
  "body": "This incident has been resolved.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "major",
444
- "last_seen": "2026-09-04T12:24:18Z",
445
  "resolved_at": "2025-10-23T18:23:35.783Z",
446
  "resolved_inferred": false,
447
  "started_at": "2025-10-23T17:32:10.000Z",
@@ -454,7 +454,7 @@
454
  "body": "This incident has been resolved.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "major",
457
- "last_seen": "2026-09-04T12:24:18Z",
458
  "resolved_at": "2025-10-21T19:24:35.170Z",
459
  "resolved_inferred": false,
460
  "started_at": "2025-10-21T17:57:56.000Z",
@@ -467,7 +467,7 @@
467
  "body": "This incident has been resolved.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "major",
470
- "last_seen": "2026-09-04T12:24:18Z",
471
  "resolved_at": "2025-10-21T03:30:49.000Z",
472
  "resolved_inferred": false,
473
  "started_at": "2025-10-21T01:27:31.000Z",
@@ -480,7 +480,7 @@
480
  "body": "This incident has been resolved.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "major",
483
- "last_seen": "2026-09-04T12:24:18Z",
484
  "resolved_at": "2025-10-20T18:00:06.000Z",
485
  "resolved_inferred": false,
486
  "started_at": "2025-10-20T17:05:31.042Z",
@@ -493,7 +493,7 @@
493
  "body": "This incident has been resolved.",
494
  "first_seen": "2026-09-04T07:06:16Z",
495
  "impact": "minor",
496
- "last_seen": "2026-09-04T12:24:18Z",
497
  "resolved_at": "2025-09-15T15:58:47.000Z",
498
  "resolved_inferred": false,
499
  "started_at": "2025-09-15T15:52:26.000Z",
@@ -506,7 +506,7 @@
506
  "body": "This incident has been resolved.",
507
  "first_seen": "2026-09-04T07:06:16Z",
508
  "impact": "major",
509
- "last_seen": "2026-09-04T12:24:18Z",
510
  "resolved_at": "2025-09-10T16:38:17.202Z",
511
  "resolved_inferred": false,
512
  "started_at": "2025-09-10T13:16:19.000Z",
@@ -519,7 +519,7 @@
519
  "body": "This incident has been resolved.",
520
  "first_seen": "2026-09-04T07:06:16Z",
521
  "impact": "major",
522
- "last_seen": "2026-09-04T12:24:18Z",
523
  "resolved_at": "2025-09-10T17:22:46.000Z",
524
  "resolved_inferred": false,
525
  "started_at": "2025-09-10T12:52:44.000Z",
@@ -532,7 +532,7 @@
532
  "body": "This incident has been resolved.",
533
  "first_seen": "2026-09-04T07:06:16Z",
534
  "impact": "major",
535
- "last_seen": "2026-09-04T12:24:18Z",
536
  "resolved_at": "2025-09-09T14:40:22.644Z",
537
  "resolved_inferred": false,
538
  "started_at": "2025-09-09T12:55:48.000Z",
@@ -545,7 +545,7 @@
545
  "body": "This incident has been resolved.",
546
  "first_seen": "2026-09-04T07:06:16Z",
547
  "impact": "major",
548
- "last_seen": "2026-09-04T12:24:18Z",
549
  "resolved_at": "2025-09-03T14:00:35.000Z",
550
  "resolved_inferred": false,
551
  "started_at": "2025-09-02T22:46:28.000Z",
@@ -558,7 +558,7 @@
558
  "body": "This incident has been resolved.",
559
  "first_seen": "2026-09-04T07:06:16Z",
560
  "impact": "minor",
561
- "last_seen": "2026-09-04T12:24:18Z",
562
  "resolved_at": "2025-08-29T22:42:39.521Z",
563
  "resolved_inferred": false,
564
  "started_at": "2025-08-29T20:28:52.056Z",
@@ -571,7 +571,7 @@
571
  "body": "This incident has been resolved.",
572
  "first_seen": "2026-09-04T07:06:16Z",
573
  "impact": "major",
574
- "last_seen": "2026-09-04T12:24:18Z",
575
  "resolved_at": "2025-08-28T20:25:35.000Z",
576
  "resolved_inferred": false,
577
  "started_at": "2025-08-28T18:30:55.000Z",
@@ -584,7 +584,7 @@
584
  "body": "This incident has been resolved.",
585
  "first_seen": "2026-09-04T07:06:16Z",
586
  "impact": "minor",
587
- "last_seen": "2026-09-04T12:24:18Z",
588
  "resolved_at": "2025-08-26T15:05:00.000Z",
589
  "resolved_inferred": false,
590
  "started_at": "2025-08-26T13:22:29.000Z",
@@ -597,7 +597,7 @@
597
  "body": "This incident has been resolved.",
598
  "first_seen": "2026-09-04T07:06:16Z",
599
  "impact": "major",
600
- "last_seen": "2026-09-04T12:24:18Z",
601
  "resolved_at": "2025-08-21T17:54:13.000Z",
602
  "resolved_inferred": false,
603
  "started_at": "2025-08-21T16:54:18.000Z",
@@ -610,7 +610,7 @@
610
  "body": "This incident has been resolved.",
611
  "first_seen": "2026-09-04T07:06:16Z",
612
  "impact": "major",
613
- "last_seen": "2026-09-04T12:24:18Z",
614
  "resolved_at": "2025-08-11T21:53:36.000Z",
615
  "resolved_inferred": false,
616
  "started_at": "2025-08-11T21:29:33.000Z",
@@ -623,7 +623,7 @@
623
  "body": "This incident has been resolved.",
624
  "first_seen": "2026-09-04T07:06:16Z",
625
  "impact": "major",
626
- "last_seen": "2026-09-04T12:24:18Z",
627
  "resolved_at": "2025-08-05T17:23:00.000Z",
628
  "resolved_inferred": false,
629
  "started_at": "2025-08-05T16:17:45.000Z",
@@ -636,7 +636,7 @@
636
  "body": "This incident has been resolved.",
637
  "first_seen": "2026-09-04T07:06:16Z",
638
  "impact": "major",
639
- "last_seen": "2026-09-04T12:24:18Z",
640
  "resolved_at": "2025-08-01T19:46:08.000Z",
641
  "resolved_inferred": false,
642
  "started_at": "2025-08-01T14:22:21.000Z",
 
3
  "slug": "pinecone",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pinecone.io",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-09-01T19:40:57.000Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-01T15:04:56.000Z",
 
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-08-25T16:11:48.000Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-25T15:50:32.000Z",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "critical",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-07-21T19:40:02.000Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-07-21T19:10:07.000Z",
 
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "minor",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-07-20T18:00:03.000Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-07-20T16:44:41.000Z",
 
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-07-13T04:15:55.000Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-07-12T23:21:10.000Z",
 
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-07-09T14:37:36.086Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-07-09T09:50:14.000Z",
 
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-06-18T18:23:35.000Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-06-18T10:00:47.000Z",
 
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "none",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-06-16T17:05:41.000Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-06-16T13:05:50.000Z",
 
116
  "body": "This incident has been resolved.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "major",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-06-06T20:40:47.000Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-06-06T17:05:39.000Z",
 
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-06-06T15:50:17.000Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-06-06T13:05:24.000Z",
 
142
  "body": "This incident has been resolved.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "minor",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2026-06-06T01:15:33.000Z",
147
  "resolved_inferred": false,
148
  "started_at": "2026-06-06T00:48:34.000Z",
 
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "major",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2026-05-25T15:00:21.000Z",
160
  "resolved_inferred": false,
161
  "started_at": "2026-05-25T13:41:50.000Z",
 
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2026-05-13T21:15:40.000Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-05-13T20:14:38.000Z",
 
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "major",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2026-05-06T20:30:10.000Z",
186
  "resolved_inferred": false,
187
  "started_at": "2026-05-06T20:02:56.000Z",
 
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2026-05-06T15:20:04.000Z",
199
  "resolved_inferred": false,
200
  "started_at": "2026-05-06T15:00:30.000Z",
 
207
  "body": "This incident has been resolved.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "major",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2026-03-13T09:53:17.000Z",
212
  "resolved_inferred": false,
213
  "started_at": "2026-03-13T08:50:03.000Z",
 
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2026-03-05T23:02:17.000Z",
225
  "resolved_inferred": false,
226
  "started_at": "2026-03-05T21:57:20.000Z",
 
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2026-03-04T22:16:28.000Z",
238
  "resolved_inferred": false,
239
  "started_at": "2026-03-04T21:06:09.000Z",
 
246
  "body": "This incident has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2026-02-24T01:52:43.000Z",
251
  "resolved_inferred": false,
252
  "started_at": "2026-02-23T23:14:35.000Z",
 
259
  "body": "This incident has been resolved.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "minor",
262
+ "last_seen": "2026-09-04T14:19:03Z",
263
  "resolved_at": "2026-02-05T21:57:04.000Z",
264
  "resolved_inferred": false,
265
  "started_at": "2026-02-05T10:55:24.000Z",
 
272
  "body": "This incident has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "major",
275
+ "last_seen": "2026-09-04T14:19:03Z",
276
  "resolved_at": "2026-01-15T15:30:56.000Z",
277
  "resolved_inferred": false,
278
  "started_at": "2026-01-15T12:12:55.000Z",
 
285
  "body": "This incident has been resolved.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "major",
288
+ "last_seen": "2026-09-04T14:19:03Z",
289
  "resolved_at": "2026-01-02T17:58:09.483Z",
290
  "resolved_inferred": false,
291
  "started_at": "2026-01-02T16:31:16.954Z",
 
298
  "body": "This incident has been resolved.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "major",
301
+ "last_seen": "2026-09-04T14:19:03Z",
302
  "resolved_at": "2025-12-31T03:29:18.000Z",
303
  "resolved_inferred": false,
304
  "started_at": "2025-12-31T03:13:07.000Z",
 
311
  "body": "From 8:15 PM to 8:50 PM UTC, some users experienced partial control plane unavailability.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "none",
314
+ "last_seen": "2026-09-04T14:19:03Z",
315
  "resolved_at": "2025-12-19T01:15:00.000Z",
316
  "resolved_inferred": false,
317
  "started_at": "2025-12-19T01:15:00.000Z",
 
324
  "body": "This incident has been resolved.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "major",
327
+ "last_seen": "2026-09-04T14:19:03Z",
328
  "resolved_at": "2025-12-15T22:02:32.693Z",
329
  "resolved_inferred": false,
330
  "started_at": "2025-12-15T10:39:51.000Z",
 
337
  "body": "This incident has been resolved.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "minor",
340
+ "last_seen": "2026-09-04T14:19:03Z",
341
  "resolved_at": "2025-12-10T01:50:19.000Z",
342
  "resolved_inferred": false,
343
  "started_at": "2025-12-09T20:15:00.000Z",
 
350
  "body": "From 3:43 PM EST to 3:50 PM EST, some embed and rerank requests were unavailable.",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "none",
353
+ "last_seen": "2026-09-04T14:19:03Z",
354
  "resolved_at": "2025-12-08T20:43:00.000Z",
355
  "resolved_inferred": false,
356
  "started_at": "2025-12-08T20:43:00.000Z",
 
363
  "body": "This incident has been resolved.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "major",
366
+ "last_seen": "2026-09-04T14:19:03Z",
367
  "resolved_at": "2025-12-05T20:42:52.000Z",
368
  "resolved_inferred": false,
369
  "started_at": "2025-12-05T18:36:46.000Z",
 
376
  "body": "This incident has been resolved.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "major",
379
+ "last_seen": "2026-09-04T14:19:03Z",
380
  "resolved_at": "2025-12-03T16:40:17.000Z",
381
  "resolved_inferred": false,
382
  "started_at": "2025-12-03T15:53:51.000Z",
 
389
  "body": "This incident has been resolved.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "major",
392
+ "last_seen": "2026-09-04T14:19:03Z",
393
  "resolved_at": "2025-11-24T18:30:05.000Z",
394
  "resolved_inferred": false,
395
  "started_at": "2025-11-24T17:28:25.000Z",
 
402
  "body": "Index-level usage metrics were unavailable for approximately 24 hours beginning at around 9:00 PM EST on November 12th",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "none",
405
+ "last_seen": "2026-09-04T14:19:03Z",
406
  "resolved_at": "2025-11-13T02:00:00.000Z",
407
  "resolved_inferred": false,
408
  "started_at": "2025-11-13T02:00:00.000Z",
 
415
  "body": "This incident has been resolved.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "major",
418
+ "last_seen": "2026-09-04T14:19:03Z",
419
  "resolved_at": "2025-11-06T14:40:24.000Z",
420
  "resolved_inferred": false,
421
  "started_at": "2025-11-06T14:38:10.000Z",
 
428
  "body": "From 4:58 PM EST to 5:10 PM EST, the cohere-rerank-3.5 model experienced partial unavailability.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "none",
431
+ "last_seen": "2026-09-04T14:19:03Z",
432
  "resolved_at": "2025-10-30T22:00:04.733Z",
433
  "resolved_inferred": false,
434
  "started_at": "2025-10-30T22:00:04.669Z",
 
441
  "body": "This incident has been resolved.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "major",
444
+ "last_seen": "2026-09-04T14:19:03Z",
445
  "resolved_at": "2025-10-23T18:23:35.783Z",
446
  "resolved_inferred": false,
447
  "started_at": "2025-10-23T17:32:10.000Z",
 
454
  "body": "This incident has been resolved.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "major",
457
+ "last_seen": "2026-09-04T14:19:03Z",
458
  "resolved_at": "2025-10-21T19:24:35.170Z",
459
  "resolved_inferred": false,
460
  "started_at": "2025-10-21T17:57:56.000Z",
 
467
  "body": "This incident has been resolved.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "major",
470
+ "last_seen": "2026-09-04T14:19:03Z",
471
  "resolved_at": "2025-10-21T03:30:49.000Z",
472
  "resolved_inferred": false,
473
  "started_at": "2025-10-21T01:27:31.000Z",
 
480
  "body": "This incident has been resolved.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "major",
483
+ "last_seen": "2026-09-04T14:19:03Z",
484
  "resolved_at": "2025-10-20T18:00:06.000Z",
485
  "resolved_inferred": false,
486
  "started_at": "2025-10-20T17:05:31.042Z",
 
493
  "body": "This incident has been resolved.",
494
  "first_seen": "2026-09-04T07:06:16Z",
495
  "impact": "minor",
496
+ "last_seen": "2026-09-04T14:19:03Z",
497
  "resolved_at": "2025-09-15T15:58:47.000Z",
498
  "resolved_inferred": false,
499
  "started_at": "2025-09-15T15:52:26.000Z",
 
506
  "body": "This incident has been resolved.",
507
  "first_seen": "2026-09-04T07:06:16Z",
508
  "impact": "major",
509
+ "last_seen": "2026-09-04T14:19:03Z",
510
  "resolved_at": "2025-09-10T16:38:17.202Z",
511
  "resolved_inferred": false,
512
  "started_at": "2025-09-10T13:16:19.000Z",
 
519
  "body": "This incident has been resolved.",
520
  "first_seen": "2026-09-04T07:06:16Z",
521
  "impact": "major",
522
+ "last_seen": "2026-09-04T14:19:03Z",
523
  "resolved_at": "2025-09-10T17:22:46.000Z",
524
  "resolved_inferred": false,
525
  "started_at": "2025-09-10T12:52:44.000Z",
 
532
  "body": "This incident has been resolved.",
533
  "first_seen": "2026-09-04T07:06:16Z",
534
  "impact": "major",
535
+ "last_seen": "2026-09-04T14:19:03Z",
536
  "resolved_at": "2025-09-09T14:40:22.644Z",
537
  "resolved_inferred": false,
538
  "started_at": "2025-09-09T12:55:48.000Z",
 
545
  "body": "This incident has been resolved.",
546
  "first_seen": "2026-09-04T07:06:16Z",
547
  "impact": "major",
548
+ "last_seen": "2026-09-04T14:19:03Z",
549
  "resolved_at": "2025-09-03T14:00:35.000Z",
550
  "resolved_inferred": false,
551
  "started_at": "2025-09-02T22:46:28.000Z",
 
558
  "body": "This incident has been resolved.",
559
  "first_seen": "2026-09-04T07:06:16Z",
560
  "impact": "minor",
561
+ "last_seen": "2026-09-04T14:19:03Z",
562
  "resolved_at": "2025-08-29T22:42:39.521Z",
563
  "resolved_inferred": false,
564
  "started_at": "2025-08-29T20:28:52.056Z",
 
571
  "body": "This incident has been resolved.",
572
  "first_seen": "2026-09-04T07:06:16Z",
573
  "impact": "major",
574
+ "last_seen": "2026-09-04T14:19:03Z",
575
  "resolved_at": "2025-08-28T20:25:35.000Z",
576
  "resolved_inferred": false,
577
  "started_at": "2025-08-28T18:30:55.000Z",
 
584
  "body": "This incident has been resolved.",
585
  "first_seen": "2026-09-04T07:06:16Z",
586
  "impact": "minor",
587
+ "last_seen": "2026-09-04T14:19:03Z",
588
  "resolved_at": "2025-08-26T15:05:00.000Z",
589
  "resolved_inferred": false,
590
  "started_at": "2025-08-26T13:22:29.000Z",
 
597
  "body": "This incident has been resolved.",
598
  "first_seen": "2026-09-04T07:06:16Z",
599
  "impact": "major",
600
+ "last_seen": "2026-09-04T14:19:03Z",
601
  "resolved_at": "2025-08-21T17:54:13.000Z",
602
  "resolved_inferred": false,
603
  "started_at": "2025-08-21T16:54:18.000Z",
 
610
  "body": "This incident has been resolved.",
611
  "first_seen": "2026-09-04T07:06:16Z",
612
  "impact": "major",
613
+ "last_seen": "2026-09-04T14:19:03Z",
614
  "resolved_at": "2025-08-11T21:53:36.000Z",
615
  "resolved_inferred": false,
616
  "started_at": "2025-08-11T21:29:33.000Z",
 
623
  "body": "This incident has been resolved.",
624
  "first_seen": "2026-09-04T07:06:16Z",
625
  "impact": "major",
626
+ "last_seen": "2026-09-04T14:19:03Z",
627
  "resolved_at": "2025-08-05T17:23:00.000Z",
628
  "resolved_inferred": false,
629
  "started_at": "2025-08-05T16:17:45.000Z",
 
636
  "body": "This incident has been resolved.",
637
  "first_seen": "2026-09-04T07:06:16Z",
638
  "impact": "major",
639
+ "last_seen": "2026-09-04T14:19:03Z",
640
  "resolved_at": "2025-08-01T19:46:08.000Z",
641
  "resolved_inferred": false,
642
  "started_at": "2025-08-01T14:22:21.000Z",
api/v/pingplotter-cloud.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "pingplotter-cloud",
4
  "platform": "instatus",
5
  "status_url": "https://status.pingplotter.cloud",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": false,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
3
  "slug": "pingplotter-cloud",
4
  "platform": "instatus",
5
  "status_url": "https://status.pingplotter.cloud",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": false,
9
  "first_watched": "2026-09-04T07:06:16Z",
api/v/pinpoint.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "pinpoint",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pinpoint.support",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "## **Email delivery disruption - 29 August to 1 September 2026**\n\n**What happened**\n\nBetween Saturday 29 August and the afternoon of Monday 31 August, and again from 23:30 BST on Monday 31 August until 11:09 BST on Tuesday 1 September, emails sent from Pinpoint were not delivered. This affected candidate communications, notifications and other outbound email across the platform.\n\n**Cause**\n\nBoth disruptions were caused by our email delivery provider, Postmark. An account restriction was applied on their side and, following its resolution, a required manual review by their team was not completed. This left the restriction in place and caused their systems to accept our emails as sent while not delivering them. No errors were returned to us, which is why the second disruption was not detected until customers reported it.\n\nPostmark has confirmed the fault was theirs, apologised, and made changes to their review process and our account settings to prevent a recurrence. No changes to Pinpoint contributed to the incident.\n\n**Resolution**\n\nOn Tuesday morning our engineering team identified that the issue was upstream and restored delivery by routing all email through a new sending channel with Postmark. Delivery was confirmed working by 11:09 BST.\n\nAll emails affected during the disruption have since been delivered. A small number of recipients may have received duplicate copies of some emails as a result of the recovery; we apologise for any confusion this caused.\n\n**What we're doing**\n\n* We have added the ability to switch email delivery channels immediately via configuration, so a similar provider-side issue can be worked around in minutes rather than hours.\n* We have expanded the notifications we receive from our provider so that account issues are visible to a wider group of our team, including out of hours.\n* We are adding monitoring on delivery volume so that a drop in delivered email is detected by us, independently of whether our provider reports an error.\n* We have formally raised the handling of this incident with Postmark and are reviewing our email delivery arrangements more broadly.\n\nWe're sorry for the disruption this caused you and your candidates. If you have any questions or have identified any specific emails you believe were not delivered, please contact your Customer Success Manager or [support@pinpointhq.com](mailto:support@pinpointhq.com).",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-09-01T15:01:59.355Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-01T08:20:01.581Z",
@@ -25,7 +25,7 @@
25
  "body": "Support Update \u2013 Resolved\n\nFin (formerly Intercom) has deployed a fix, and the issue now appears to be resolved. Our team once again has access to the support inbox and is responding to your queries.\n\nWe'll continue to monitor the situation closely in case anything changes. Thank you for your patience while this issue was being resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-08-03T16:42:56.309Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-03T14:33:16.449Z",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-06-06T00:30:36.212Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-06-05T12:33:25.942Z",
@@ -51,7 +51,7 @@
51
  "body": "**Duration:** Approximately 4 hours of intermittent disruption \\(03:00 \u2013 06:51 UTC\\), with two distinct impact windows.\n\n## What Happened\n\nPinpoint experienced an unexpected service disruption in the early hours of 13 May. The incident had two impact windows: an initial period of unavailability between approximately 03:00 and 04:00 UTC, and a follow-on period between approximately 05:39 and 06:51 UTC during which users attempting to modify certain types of records \\(predominantly scorecard submissions\\) encountered errors.\n\nNo data was lost or corrupted, and no background jobs were delayed.\n\n## Timeline \\(UTC\\)\n\n* 03:00 \n Initial impact begins; application unavailable.\n* 04:00 \n Initial impact resolves; engineering team investigating.\n* 05:39 \n Second impact window begins; errors on a subset of record updates.\n* 06:29 \n Status page warning posted.\n* 06:51 \n Second impact window resolves.\n* 07:04 \n Incident marked as resolved.\n\n## Why It Happened\n\nThe disruption was caused by an unexpected interaction between a routine internal database operation and an active background process. This combination of events is an outlier we had not previously encountered or anticipated. The root cause has been fully investigated and is understood.\n\n## What We're Doing About It\n\n* **Additional Monitoring** \n We have put additional monitoring in place to detect this specific class of interaction much earlier, before it can cause customer impact.\n* **Increased Database Capacity** \n We have provisioned additional database capacity to further reduce the likelihood of recurrence.\n\n_We sincerely apologise for the disruption and appreciate your patience._",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "critical",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-05-13T07:04:33.671Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-05-13T06:29:14.000Z",
@@ -64,7 +64,7 @@
64
  "body": "**Date:** 19 March 2026\n\n**Duration:** Approximately 35 minutes \\(11:46 to 12:21 UTC\\).\n\n### What Happened\n\nPinpoint experienced a service outage beginning at approximately 11:46 UTC on 19 March. Users were unable to access the platform and received 503 errors. Full service was restored by approximately 12:21 UTC. No data was lost or corrupted.\n\n### Timeline \\(UTC\\)\n\n* **11:46** - Automated monitoring alerts triggered for service unavailability.\n* **11:47** - Engineering team began investigating.\n* **12:01** - Status page updated to reflect the incident.\n* **12:10** - Root cause identified as a database firewall misconfiguration introduced during an infrastructure change.\n* **12:20** - Fix applied; service restored.\n* **12:21** - Incident marked as resolved.\n\n### Why It Happened\n\nDuring an infrastructure configuration change, a database firewall rule was inadvertently applied with an overly restrictive scope. This prevented our application servers from connecting to the primary database, causing all requests to fail.\n\n### What We're Doing About It\n\n* **Immediate fix:** The firewall configuration has been corrected and verified.\n* **Hardening:** We are making production database firewall rules explicitly immutable and tightening API token permissions to prevent unexpected firewall modifications.\n\nWe sincerely apologise for the disruption and appreciate your patience.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "major",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-03-19T12:21:23.372Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-03-19T12:01:17.301Z",
@@ -77,7 +77,7 @@
77
  "body": "> What happened\nUsers were unable to preview CVs and cover letters within the platform. The preview area appeared blank or showed a \"blocked by browser\" message. Downloading resumes continued to work normally throughout.\n\n> What caused it\nA security update was deployed overnight to protect admins from potentially harmful files. While the protection worked as intended, it had an unintended side effect - it also prevented the resume preview from loading correctly in all browsers.\n\n> What we did\nIdentified the cause within minutes of being alerted\nDeployed a fix to restore normal resume previewing\n\n> What's next\nWe have applied an alternative security protection using a different approach that doesn't affect the preview.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-03-18T10:02:00.360Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-03-18T08:22:01.003Z",
@@ -90,7 +90,7 @@
90
  "body": "Component: Pinpoint \u2192 Partial Outage\n\nInvestigating - 05:00 UTC:\n> We are aware that some users may be unable to perform actions that involve saving or updating data. Our engineering team is actively investigating.\n\nIdentified - 06:45 UTC:\n> The auto-scaling configured on our primary database infrastructure failed to provision additional storage in response to increased load. As a result, the database entered read-only mode, preventing write operations. We are provisioning additional storage to restore full functionality.\n\nMonitoring - 06:57 UTC:\n> Additional storage has been provisioned and write operations have been restored. Our team is monitoring to confirm full stability across all services.\n\nResolved - 07:01 UTC:\n> The issue has been fully resolved and all services are operating normally. We apologise for the disruption and are reviewing our auto-scaling configuration to prevent recurrence.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-03-03T05:00:00.000Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-03-03T05:00:00.000Z",
@@ -103,7 +103,7 @@
103
  "body": "**Date:** 12 February 2026\n\n**Duration:** Approximately 30 minutes \\(14:00 - 14:35 UTC\\), with a brief secondary disruption during recovery.\n\n### What Happened\n\nPinpoint experienced a service outage beginning at approximately 14:00 UTC on 12 February. Most users were unable to access the platform and received 504 timeout errors, though partial capacity meant some requests were still being served. Full service was restored by approximately 14:35 UTC.\n\nSome outbound emails were delayed due to background workers also being affected. All queued emails were delivered by approximately 16:15 UTC. No data was lost or corrupted.\n\n### Timeline \\(UTC\\)\n\n* **14:00** - Automated monitoring alerts triggered for service unavailability.\n* **14:02** - Engineering team began investigating.\n* **14:08** - Root cause identified as a network configuration conflict introduced by a third-party infrastructure provider.\n* **14:20** - Initial fix applied; service stabilising.\n* **14:22** - Third-party provider's automation reinstated the conflicting configuration, causing a brief secondary disruption.\n* **14:30** - Fix reapplied with additional safeguards to prevent recurrence.\n* **14:35** - Full service restored.\n* **16:15** - All delayed outbound emails delivered.\n\n### Why It Happened\n\nA third-party infrastructure provider applied an automated network configuration change to our servers. The change was overly broad and conflicted with our own networking configuration, causing the majority of inbound traffic to be dropped. During initial recovery, the provider's automation re-applied the conflicting change before we implemented stronger protections.\n\n### What We're Doing About It\n\n* **Immediate Safeguards:** Protections are in place to prevent this specific change from affecting our infrastructure again.\n* **Removing the Dependency:** We are accelerating work to bring the affected networking functionality fully in-house, removing the third-party dependency entirely.\n\nWe sincerely apologise for the disruption and appreciate your patience.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "major",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-02-12T15:02:21.310Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-02-12T14:05:09.069Z",
@@ -116,7 +116,7 @@
116
  "body": "We have identified the missing records within the platform and restored the affected data.\n\nIf you have any questions or require assistance please reach out to our support team via the in-app chat function",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "none",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2025-11-30T19:30:00.929Z",
121
  "resolved_inferred": false,
122
  "started_at": "2025-11-28T12:03:37.000Z",
@@ -129,7 +129,7 @@
129
  "body": "This incident has been resolved.\n\n> What happened\nFollowing a planned infrastructure update last night, some customers experienced errors when performing certain actions on the platform, particularly around candidate pages and interview scheduling. We identified the root cause and restored full service by reverting to our previous database infrastructure.\n\n> Current status\nThe platform is now fully operational. All features are working normally.\n\n> Data impact\nDue to an issue between both database providers when we restored service, there's a short window (between 10:16 and 10:57 UTC this morning) where some changes made on the platform may not yet be reflected. No data has been lost, we have complete records of everything that happened during this window and are working to restore any affected changes to the live system.\n\nThe status of data reconciliation is being tracked here: https://status.pinpoint.support/incidents/9v65gddb3y1n\n\n> A note on our recovery standards\nWe maintain internal Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) as part of our commitment to platform reliability. The 41-minute data gap from this incident falls outside the standards we set for ourselves, and we take that seriously. While no data was lost, we're treating this as a priority learning for our infrastructure processes going forward, and feedback for our vendors and their practices. \n\nA full post-mortem will follow on Monday.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "major",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2025-11-28T11:31:48.000Z",
134
  "resolved_inferred": false,
135
  "started_at": "2025-11-28T10:33:30.000Z",
 
3
  "slug": "pinpoint",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pinpoint.support",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "## **Email delivery disruption - 29 August to 1 September 2026**\n\n**What happened**\n\nBetween Saturday 29 August and the afternoon of Monday 31 August, and again from 23:30 BST on Monday 31 August until 11:09 BST on Tuesday 1 September, emails sent from Pinpoint were not delivered. This affected candidate communications, notifications and other outbound email across the platform.\n\n**Cause**\n\nBoth disruptions were caused by our email delivery provider, Postmark. An account restriction was applied on their side and, following its resolution, a required manual review by their team was not completed. This left the restriction in place and caused their systems to accept our emails as sent while not delivering them. No errors were returned to us, which is why the second disruption was not detected until customers reported it.\n\nPostmark has confirmed the fault was theirs, apologised, and made changes to their review process and our account settings to prevent a recurrence. No changes to Pinpoint contributed to the incident.\n\n**Resolution**\n\nOn Tuesday morning our engineering team identified that the issue was upstream and restored delivery by routing all email through a new sending channel with Postmark. Delivery was confirmed working by 11:09 BST.\n\nAll emails affected during the disruption have since been delivered. A small number of recipients may have received duplicate copies of some emails as a result of the recovery; we apologise for any confusion this caused.\n\n**What we're doing**\n\n* We have added the ability to switch email delivery channels immediately via configuration, so a similar provider-side issue can be worked around in minutes rather than hours.\n* We have expanded the notifications we receive from our provider so that account issues are visible to a wider group of our team, including out of hours.\n* We are adding monitoring on delivery volume so that a drop in delivered email is detected by us, independently of whether our provider reports an error.\n* We have formally raised the handling of this incident with Postmark and are reviewing our email delivery arrangements more broadly.\n\nWe're sorry for the disruption this caused you and your candidates. If you have any questions or have identified any specific emails you believe were not delivered, please contact your Customer Success Manager or [support@pinpointhq.com](mailto:support@pinpointhq.com).",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-09-01T15:01:59.355Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-01T08:20:01.581Z",
 
25
  "body": "Support Update \u2013 Resolved\n\nFin (formerly Intercom) has deployed a fix, and the issue now appears to be resolved. Our team once again has access to the support inbox and is responding to your queries.\n\nWe'll continue to monitor the situation closely in case anything changes. Thank you for your patience while this issue was being resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "minor",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-08-03T16:42:56.309Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-03T14:33:16.449Z",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-06-06T00:30:36.212Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-06-05T12:33:25.942Z",
 
51
  "body": "**Duration:** Approximately 4 hours of intermittent disruption \\(03:00 \u2013 06:51 UTC\\), with two distinct impact windows.\n\n## What Happened\n\nPinpoint experienced an unexpected service disruption in the early hours of 13 May. The incident had two impact windows: an initial period of unavailability between approximately 03:00 and 04:00 UTC, and a follow-on period between approximately 05:39 and 06:51 UTC during which users attempting to modify certain types of records \\(predominantly scorecard submissions\\) encountered errors.\n\nNo data was lost or corrupted, and no background jobs were delayed.\n\n## Timeline \\(UTC\\)\n\n* 03:00 \n Initial impact begins; application unavailable.\n* 04:00 \n Initial impact resolves; engineering team investigating.\n* 05:39 \n Second impact window begins; errors on a subset of record updates.\n* 06:29 \n Status page warning posted.\n* 06:51 \n Second impact window resolves.\n* 07:04 \n Incident marked as resolved.\n\n## Why It Happened\n\nThe disruption was caused by an unexpected interaction between a routine internal database operation and an active background process. This combination of events is an outlier we had not previously encountered or anticipated. The root cause has been fully investigated and is understood.\n\n## What We're Doing About It\n\n* **Additional Monitoring** \n We have put additional monitoring in place to detect this specific class of interaction much earlier, before it can cause customer impact.\n* **Increased Database Capacity** \n We have provisioned additional database capacity to further reduce the likelihood of recurrence.\n\n_We sincerely apologise for the disruption and appreciate your patience._",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "critical",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-05-13T07:04:33.671Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-05-13T06:29:14.000Z",
 
64
  "body": "**Date:** 19 March 2026\n\n**Duration:** Approximately 35 minutes \\(11:46 to 12:21 UTC\\).\n\n### What Happened\n\nPinpoint experienced a service outage beginning at approximately 11:46 UTC on 19 March. Users were unable to access the platform and received 503 errors. Full service was restored by approximately 12:21 UTC. No data was lost or corrupted.\n\n### Timeline \\(UTC\\)\n\n* **11:46** - Automated monitoring alerts triggered for service unavailability.\n* **11:47** - Engineering team began investigating.\n* **12:01** - Status page updated to reflect the incident.\n* **12:10** - Root cause identified as a database firewall misconfiguration introduced during an infrastructure change.\n* **12:20** - Fix applied; service restored.\n* **12:21** - Incident marked as resolved.\n\n### Why It Happened\n\nDuring an infrastructure configuration change, a database firewall rule was inadvertently applied with an overly restrictive scope. This prevented our application servers from connecting to the primary database, causing all requests to fail.\n\n### What We're Doing About It\n\n* **Immediate fix:** The firewall configuration has been corrected and verified.\n* **Hardening:** We are making production database firewall rules explicitly immutable and tightening API token permissions to prevent unexpected firewall modifications.\n\nWe sincerely apologise for the disruption and appreciate your patience.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "major",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-03-19T12:21:23.372Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-03-19T12:01:17.301Z",
 
77
  "body": "> What happened\nUsers were unable to preview CVs and cover letters within the platform. The preview area appeared blank or showed a \"blocked by browser\" message. Downloading resumes continued to work normally throughout.\n\n> What caused it\nA security update was deployed overnight to protect admins from potentially harmful files. While the protection worked as intended, it had an unintended side effect - it also prevented the resume preview from loading correctly in all browsers.\n\n> What we did\nIdentified the cause within minutes of being alerted\nDeployed a fix to restore normal resume previewing\n\n> What's next\nWe have applied an alternative security protection using a different approach that doesn't affect the preview.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "minor",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-03-18T10:02:00.360Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-03-18T08:22:01.003Z",
 
90
  "body": "Component: Pinpoint \u2192 Partial Outage\n\nInvestigating - 05:00 UTC:\n> We are aware that some users may be unable to perform actions that involve saving or updating data. Our engineering team is actively investigating.\n\nIdentified - 06:45 UTC:\n> The auto-scaling configured on our primary database infrastructure failed to provision additional storage in response to increased load. As a result, the database entered read-only mode, preventing write operations. We are provisioning additional storage to restore full functionality.\n\nMonitoring - 06:57 UTC:\n> Additional storage has been provisioned and write operations have been restored. Our team is monitoring to confirm full stability across all services.\n\nResolved - 07:01 UTC:\n> The issue has been fully resolved and all services are operating normally. We apologise for the disruption and are reviewing our auto-scaling configuration to prevent recurrence.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-03-03T05:00:00.000Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-03-03T05:00:00.000Z",
 
103
  "body": "**Date:** 12 February 2026\n\n**Duration:** Approximately 30 minutes \\(14:00 - 14:35 UTC\\), with a brief secondary disruption during recovery.\n\n### What Happened\n\nPinpoint experienced a service outage beginning at approximately 14:00 UTC on 12 February. Most users were unable to access the platform and received 504 timeout errors, though partial capacity meant some requests were still being served. Full service was restored by approximately 14:35 UTC.\n\nSome outbound emails were delayed due to background workers also being affected. All queued emails were delivered by approximately 16:15 UTC. No data was lost or corrupted.\n\n### Timeline \\(UTC\\)\n\n* **14:00** - Automated monitoring alerts triggered for service unavailability.\n* **14:02** - Engineering team began investigating.\n* **14:08** - Root cause identified as a network configuration conflict introduced by a third-party infrastructure provider.\n* **14:20** - Initial fix applied; service stabilising.\n* **14:22** - Third-party provider's automation reinstated the conflicting configuration, causing a brief secondary disruption.\n* **14:30** - Fix reapplied with additional safeguards to prevent recurrence.\n* **14:35** - Full service restored.\n* **16:15** - All delayed outbound emails delivered.\n\n### Why It Happened\n\nA third-party infrastructure provider applied an automated network configuration change to our servers. The change was overly broad and conflicted with our own networking configuration, causing the majority of inbound traffic to be dropped. During initial recovery, the provider's automation re-applied the conflicting change before we implemented stronger protections.\n\n### What We're Doing About It\n\n* **Immediate Safeguards:** Protections are in place to prevent this specific change from affecting our infrastructure again.\n* **Removing the Dependency:** We are accelerating work to bring the affected networking functionality fully in-house, removing the third-party dependency entirely.\n\nWe sincerely apologise for the disruption and appreciate your patience.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "major",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-02-12T15:02:21.310Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-02-12T14:05:09.069Z",
 
116
  "body": "We have identified the missing records within the platform and restored the affected data.\n\nIf you have any questions or require assistance please reach out to our support team via the in-app chat function",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "none",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2025-11-30T19:30:00.929Z",
121
  "resolved_inferred": false,
122
  "started_at": "2025-11-28T12:03:37.000Z",
 
129
  "body": "This incident has been resolved.\n\n> What happened\nFollowing a planned infrastructure update last night, some customers experienced errors when performing certain actions on the platform, particularly around candidate pages and interview scheduling. We identified the root cause and restored full service by reverting to our previous database infrastructure.\n\n> Current status\nThe platform is now fully operational. All features are working normally.\n\n> Data impact\nDue to an issue between both database providers when we restored service, there's a short window (between 10:16 and 10:57 UTC this morning) where some changes made on the platform may not yet be reflected. No data has been lost, we have complete records of everything that happened during this window and are working to restore any affected changes to the live system.\n\nThe status of data reconciliation is being tracked here: https://status.pinpoint.support/incidents/9v65gddb3y1n\n\n> A note on our recovery standards\nWe maintain internal Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) as part of our commitment to platform reliability. The 41-minute data gap from this incident falls outside the standards we set for ourselves, and we take that seriously. While no data was lost, we're treating this as a priority learning for our infrastructure processes going forward, and feedback for our vendors and their practices. \n\nA full post-mortem will follow on Monday.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "major",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2025-11-28T11:31:48.000Z",
134
  "resolved_inferred": false,
135
  "started_at": "2025-11-28T10:33:30.000Z",
api/v/pipedream.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "pipedream",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pipedream.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-07-29T00:34:19.204Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-07-29T00:06:19.110Z",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "critical",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-07-28T23:59:12.315Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-07-28T23:40:36.202Z",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-07-14T18:33:37.552Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-07-14T17:45:25.106Z",
@@ -51,7 +51,7 @@
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-05-03T19:15:35.654Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-05-01T03:53:24.517Z",
@@ -64,7 +64,7 @@
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-04-24T02:47:13.075Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-04-24T02:07:18.111Z",
@@ -77,7 +77,7 @@
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-04-07T17:30:00.000Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-04-07T17:30:00.000Z",
@@ -90,7 +90,7 @@
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-02-24T00:45:58.881Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-02-24T00:39:13.886Z",
@@ -103,7 +103,7 @@
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "none",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-02-09T17:35:29.286Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-02-09T12:21:27.903Z",
@@ -116,7 +116,7 @@
116
  "body": "We have deployed a fix and are monitoring",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "none",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-02-02T21:08:15.000Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-02-02T16:53:40.857Z",
@@ -129,7 +129,7 @@
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "major",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-01-13T00:51:08.110Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-01-12T23:31:21.164Z",
@@ -142,7 +142,7 @@
142
  "body": "Our front end services experienced unusual request patterns which led to degraded performance. We have updated our systems to address the issue and performance has returned to normal levels.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "none",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2025-11-20T02:17:26.855Z",
147
  "resolved_inferred": false,
148
  "started_at": "2025-11-19T13:15:14.000Z",
@@ -155,7 +155,7 @@
155
  "body": "root cause identified, Short term Mitigation efforts have been successful. Long term Mitigation solution has been identified and will be implemented as soon as the fix has passed our QA processes.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "none",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2025-11-04T19:14:29.695Z",
160
  "resolved_inferred": false,
161
  "started_at": "2025-11-04T15:53:47.870Z",
@@ -168,7 +168,7 @@
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "none",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2025-10-21T01:26:26.327Z",
173
  "resolved_inferred": false,
174
  "started_at": "2025-10-20T13:10:58.984Z",
@@ -181,7 +181,7 @@
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "major",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2025-09-16T19:09:54.488Z",
186
  "resolved_inferred": false,
187
  "started_at": "2025-09-16T17:56:02.621Z",
@@ -194,7 +194,7 @@
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2025-09-02T18:32:45.229Z",
199
  "resolved_inferred": false,
200
  "started_at": "2025-09-02T16:38:19.066Z",
@@ -207,7 +207,7 @@
207
  "body": "This incident has been resolved.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "minor",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2025-08-22T20:51:20.659Z",
212
  "resolved_inferred": false,
213
  "started_at": "2025-08-21T18:46:51.000Z",
@@ -220,7 +220,7 @@
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2025-08-21T19:40:40.088Z",
225
  "resolved_inferred": false,
226
  "started_at": "2025-08-21T17:23:34.000Z",
@@ -233,7 +233,7 @@
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "none",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2025-08-16T00:51:23.029Z",
238
  "resolved_inferred": false,
239
  "started_at": "2025-08-15T23:40:31.384Z",
@@ -246,7 +246,7 @@
246
  "body": "This incident has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2025-08-11T16:57:43.585Z",
251
  "resolved_inferred": false,
252
  "started_at": "2025-08-09T15:43:12.000Z",
 
3
  "slug": "pipedream",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pipedream.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-07-29T00:34:19.204Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-07-29T00:06:19.110Z",
 
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "critical",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-07-28T23:59:12.315Z",
30
  "resolved_inferred": false,
31
  "started_at": "2026-07-28T23:40:36.202Z",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "minor",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-07-14T18:33:37.552Z",
43
  "resolved_inferred": false,
44
  "started_at": "2026-07-14T17:45:25.106Z",
 
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-05-03T19:15:35.654Z",
56
  "resolved_inferred": false,
57
  "started_at": "2026-05-01T03:53:24.517Z",
 
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "minor",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-04-24T02:47:13.075Z",
69
  "resolved_inferred": false,
70
  "started_at": "2026-04-24T02:07:18.111Z",
 
77
  "body": "This incident has been resolved.",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "major",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-04-07T17:30:00.000Z",
82
  "resolved_inferred": false,
83
  "started_at": "2026-04-07T17:30:00.000Z",
 
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "minor",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-02-24T00:45:58.881Z",
95
  "resolved_inferred": false,
96
  "started_at": "2026-02-24T00:39:13.886Z",
 
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "none",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-02-09T17:35:29.286Z",
108
  "resolved_inferred": false,
109
  "started_at": "2026-02-09T12:21:27.903Z",
 
116
  "body": "We have deployed a fix and are monitoring",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "none",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-02-02T21:08:15.000Z",
121
  "resolved_inferred": false,
122
  "started_at": "2026-02-02T16:53:40.857Z",
 
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "major",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-01-13T00:51:08.110Z",
134
  "resolved_inferred": false,
135
  "started_at": "2026-01-12T23:31:21.164Z",
 
142
  "body": "Our front end services experienced unusual request patterns which led to degraded performance. We have updated our systems to address the issue and performance has returned to normal levels.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "none",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2025-11-20T02:17:26.855Z",
147
  "resolved_inferred": false,
148
  "started_at": "2025-11-19T13:15:14.000Z",
 
155
  "body": "root cause identified, Short term Mitigation efforts have been successful. Long term Mitigation solution has been identified and will be implemented as soon as the fix has passed our QA processes.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "none",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2025-11-04T19:14:29.695Z",
160
  "resolved_inferred": false,
161
  "started_at": "2025-11-04T15:53:47.870Z",
 
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "none",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2025-10-21T01:26:26.327Z",
173
  "resolved_inferred": false,
174
  "started_at": "2025-10-20T13:10:58.984Z",
 
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "major",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2025-09-16T19:09:54.488Z",
186
  "resolved_inferred": false,
187
  "started_at": "2025-09-16T17:56:02.621Z",
 
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "minor",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2025-09-02T18:32:45.229Z",
199
  "resolved_inferred": false,
200
  "started_at": "2025-09-02T16:38:19.066Z",
 
207
  "body": "This incident has been resolved.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "minor",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2025-08-22T20:51:20.659Z",
212
  "resolved_inferred": false,
213
  "started_at": "2025-08-21T18:46:51.000Z",
 
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2025-08-21T19:40:40.088Z",
225
  "resolved_inferred": false,
226
  "started_at": "2025-08-21T17:23:34.000Z",
 
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "none",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2025-08-16T00:51:23.029Z",
238
  "resolved_inferred": false,
239
  "started_at": "2025-08-15T23:40:31.384Z",
 
246
  "body": "This incident has been resolved.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "major",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2025-08-11T16:57:43.585Z",
251
  "resolved_inferred": false,
252
  "started_at": "2025-08-09T15:43:12.000Z",
api/v/pipefy.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "pipefy",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pipefy.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "The incident was resolved",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-08-26T20:39:09Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-26T20:27:46Z",
@@ -24,7 +24,7 @@
24
  "body": "The incident was resolved after the domain was unblocked by the provider.",
25
  "first_seen": "2026-09-04T07:06:16Z",
26
  "impact": "minor",
27
- "last_seen": "2026-09-04T12:24:18Z",
28
  "resolved_at": "2026-08-17T21:07:11Z",
29
  "resolved_inferred": false,
30
  "started_at": "2026-08-17T16:44:09Z",
@@ -36,7 +36,7 @@
36
  "body": "**Latest update**\nThe incident has been resolved following mitigation by the team",
37
  "first_seen": "2026-09-04T07:06:16Z",
38
  "impact": "minor",
39
- "last_seen": "2026-09-04T12:24:18Z",
40
  "resolved_at": "2026-07-16T18:56:16Z",
41
  "resolved_inferred": false,
42
  "started_at": "2026-07-16T18:52:16Z",
@@ -48,7 +48,7 @@
48
  "body": "AI service Routing is working as expected and all AI services are back to normal.",
49
  "first_seen": "2026-09-04T07:06:16Z",
50
  "impact": "minor",
51
- "last_seen": "2026-09-04T12:24:18Z",
52
  "resolved_at": "2026-07-08T22:16:37Z",
53
  "resolved_inferred": false,
54
  "started_at": "2026-07-08T20:24:43Z",
@@ -60,7 +60,7 @@
60
  "body": "The incident was resolved",
61
  "first_seen": "2026-09-04T07:06:16Z",
62
  "impact": "minor",
63
- "last_seen": "2026-09-04T12:24:18Z",
64
  "resolved_at": "2026-06-15T20:46:36Z",
65
  "resolved_inferred": false,
66
  "started_at": "2026-06-15T20:45:34Z",
@@ -72,7 +72,7 @@
72
  "body": "The incident was resolved",
73
  "first_seen": "2026-09-04T07:06:16Z",
74
  "impact": "minor",
75
- "last_seen": "2026-09-04T12:24:18Z",
76
  "resolved_at": "2026-06-15T20:23:48Z",
77
  "resolved_inferred": false,
78
  "started_at": "2026-06-15T20:07:21Z",
@@ -84,7 +84,7 @@
84
  "body": "The incident was resolved",
85
  "first_seen": "2026-09-04T07:06:16Z",
86
  "impact": "minor",
87
- "last_seen": "2026-09-04T12:24:18Z",
88
  "resolved_at": "2026-06-03T20:47:24Z",
89
  "resolved_inferred": false,
90
  "started_at": "2026-06-03T20:38:50Z",
@@ -96,7 +96,7 @@
96
  "body": "This incident has been resolved.",
97
  "first_seen": "2026-09-04T07:06:16Z",
98
  "impact": "major",
99
- "last_seen": "2026-09-04T12:24:18Z",
100
  "resolved_at": "2026-05-28T17:50:46Z",
101
  "resolved_inferred": false,
102
  "started_at": "2026-05-28T17:49:46Z",
@@ -108,7 +108,7 @@
108
  "body": "A fix was applied, and the incident was resolved.",
109
  "first_seen": "2026-09-04T07:06:16Z",
110
  "impact": "none",
111
- "last_seen": "2026-09-04T12:24:18Z",
112
  "resolved_at": "2026-05-28T17:00:14Z",
113
  "resolved_inferred": false,
114
  "started_at": "2026-05-28T16:41:53Z",
@@ -120,7 +120,7 @@
120
  "body": "This incident has been resolved.",
121
  "first_seen": "2026-09-04T07:06:16Z",
122
  "impact": "minor",
123
- "last_seen": "2026-09-04T12:24:18Z",
124
  "resolved_at": "2026-05-19T19:47:02Z",
125
  "resolved_inferred": false,
126
  "started_at": "2026-05-19T20:08:38Z",
@@ -132,7 +132,7 @@
132
  "body": "**Root Cause**\n\nThe issue was caused by an automation process that affected the system's performance. During this time, the speed of processing tasks was slower than usual, impacting the overall efficiency.\n\n**Resolution**\n\nThe problematic automation was removed, which restored the system's performance back to its normal state, ensuring that operations could continue smoothly.",
133
  "first_seen": "2026-09-04T07:06:16Z",
134
  "impact": "minor",
135
- "last_seen": "2026-09-04T12:24:18Z",
136
  "resolved_at": "2026-05-13T21:51:03Z",
137
  "resolved_inferred": false,
138
  "started_at": "2026-05-13T21:08:41Z",
@@ -144,7 +144,7 @@
144
  "body": "**Root Cause**\n\nThe issue was traced back to a firmware update in a database instance, which led to a failure in the system's ability to switch over to a backup. This caused the main application to go down.\n\n**Resolution**\n\nThe problem was resolved by starting the database on a new healthy instance, restoring the system's functionality.\n\n**Action Plan**\n\n- To prevent future occurrences, a manual switch-over will be performed before any instance restarts. \n- Additionally, a maintenance is scheduled for the system update to address the identified bug.",
145
  "first_seen": "2026-09-04T07:06:16Z",
146
  "impact": "critical",
147
- "last_seen": "2026-09-04T12:24:18Z",
148
  "resolved_at": "2026-05-08T22:59:56Z",
149
  "resolved_inferred": false,
150
  "started_at": "2026-05-08T23:06:26Z",
@@ -156,7 +156,7 @@
156
  "body": "This incident was resolved after a fix being implemented",
157
  "first_seen": "2026-09-04T07:06:16Z",
158
  "impact": "none",
159
- "last_seen": "2026-09-04T12:24:18Z",
160
  "resolved_at": "2026-05-05T19:35:23Z",
161
  "resolved_inferred": false,
162
  "started_at": "2026-05-05T15:06:41Z",
@@ -168,7 +168,7 @@
168
  "body": "**Root Cause**\n\nThe application experienced performance issues due to a spike in executing flows that affected the app's performance. During the investigation, an issue was identified, requiring a fix to resolve the problem permanently.\n\n**Resolution**\n\nA fix to address the issue was implemented in the application, ensuring the application's performance returned to normal.\n\n**Action Plan**\n\nThe team will monitor new metrics in the scenario, to avoid the future impact",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "minor",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2026-05-04T19:48:21Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-05-04T19:06:34Z",
@@ -180,7 +180,7 @@
180
  "body": "Some new performance patches was applied during the monitoring period and we consider the incident resolved now.\r\nThe app performance is back to an expected level and all operations are running normally. \r\n\r\nWe apologize for the incident and the entire team evolved both technically and operationally to prevent this in the future.",
181
  "first_seen": "2026-09-04T07:06:16Z",
182
  "impact": "none",
183
- "last_seen": "2026-09-04T12:24:18Z",
184
  "resolved_at": "2017-06-30T13:48:57Z",
185
  "resolved_inferred": false,
186
  "started_at": "2026-04-23T18:48:49Z",
@@ -192,7 +192,7 @@
192
  "body": "This incident has been resolved.",
193
  "first_seen": "2026-09-04T07:06:16Z",
194
  "impact": "none",
195
- "last_seen": "2026-09-04T12:24:18Z",
196
  "resolved_at": "2017-10-13T18:16:23Z",
197
  "resolved_inferred": false,
198
  "started_at": "2026-04-23T18:48:48Z",
@@ -204,7 +204,7 @@
204
  "body": "All data is restored and reindexed again in our Elastic Search.\r\n\r\nWe are investigating whats happen in a post mortem meeting and find a better solution to prevent that it's happens again.",
205
  "first_seen": "2026-09-04T07:06:16Z",
206
  "impact": "none",
207
- "last_seen": "2026-09-04T12:24:18Z",
208
  "resolved_at": "2017-10-09T22:51:49Z",
209
  "resolved_inferred": false,
210
  "started_at": "2026-04-23T18:48:48Z",
@@ -216,7 +216,7 @@
216
  "body": "This incident has been resolved.\r\n\r\nToday at 1:58 PM (UTC) our monitoring service identified a failure to communicate with the Redis database service responsible for background jobs.\r\n\r\nAt 2:00 PM (UTC) our team decided to put our disaster recovery in action, creating a new database that was finished successfully at 14:10 (UTC).\r\n\r\nOur automated test was run to check the overall status of the system. We've also put it online again for all users at 14:12 (UTC).",
217
  "first_seen": "2026-09-04T07:06:16Z",
218
  "impact": "none",
219
- "last_seen": "2026-09-04T12:24:18Z",
220
  "resolved_at": "2017-09-04T14:26:00Z",
221
  "resolved_inferred": false,
222
  "started_at": "2026-04-23T18:48:48Z",
@@ -228,7 +228,7 @@
228
  "body": "This incident has been resolved.",
229
  "first_seen": "2026-09-04T07:06:16Z",
230
  "impact": "none",
231
- "last_seen": "2026-09-04T12:24:18Z",
232
  "resolved_at": "2017-08-15T19:07:39Z",
233
  "resolved_inferred": false,
234
  "started_at": "2026-04-23T18:48:48Z",
@@ -240,7 +240,7 @@
240
  "body": "During a Redis migration our team identified a failure in HA, provided by our PaaS, which didn't run as expected.\r\nThat failure occurred between 0:14 AM and 0:17 AM (UTC) and was promptly handled by our Ops Team.",
241
  "first_seen": "2026-09-04T07:06:16Z",
242
  "impact": "none",
243
- "last_seen": "2026-09-04T12:24:18Z",
244
  "resolved_at": "2018-03-16T00:14:00Z",
245
  "resolved_inferred": false,
246
  "started_at": "2026-04-23T18:48:47Z",
@@ -252,7 +252,7 @@
252
  "body": "This incident has been resolved.",
253
  "first_seen": "2026-09-04T07:06:16Z",
254
  "impact": "none",
255
- "last_seen": "2026-09-04T12:24:18Z",
256
  "resolved_at": "2018-02-26T14:46:27Z",
257
  "resolved_inferred": false,
258
  "started_at": "2026-04-23T18:48:47Z",
@@ -264,7 +264,7 @@
264
  "body": "This incident has been resolved.",
265
  "first_seen": "2026-09-04T07:06:16Z",
266
  "impact": "none",
267
- "last_seen": "2026-09-04T12:24:18Z",
268
  "resolved_at": "2018-01-19T20:46:00Z",
269
  "resolved_inferred": false,
270
  "started_at": "2026-04-23T18:48:47Z",
@@ -276,7 +276,7 @@
276
  "body": "The tests were successful and the system is working again.\r\n\r\nWe are working to improving this script so that this problem does not happen again.",
277
  "first_seen": "2026-09-04T07:06:16Z",
278
  "impact": "none",
279
- "last_seen": "2026-09-04T12:24:18Z",
280
  "resolved_at": "2017-11-05T07:32:40Z",
281
  "resolved_inferred": false,
282
  "started_at": "2026-04-23T18:48:47Z",
@@ -288,7 +288,7 @@
288
  "body": "This incident has been resolved.",
289
  "first_seen": "2026-09-04T07:06:16Z",
290
  "impact": "none",
291
- "last_seen": "2026-09-04T12:24:18Z",
292
  "resolved_at": "2017-10-16T20:34:29Z",
293
  "resolved_inferred": false,
294
  "started_at": "2026-04-23T18:48:47Z",
@@ -300,7 +300,7 @@
300
  "body": "We identify the problem, it happened because the gem [sequenced](https://github.com/derrickreimer/sequenced) that we use in our Ruby project locked the phase table, after that this process died and table stay locked.\r\n\r\nWe kill the process and restart the application that returns to respond as expected. Now we are removing that gem and move this logic to our database that can do this job in the same process and prevent this error.",
301
  "first_seen": "2026-09-04T07:06:16Z",
302
  "impact": "none",
303
- "last_seen": "2026-09-04T12:24:18Z",
304
  "resolved_at": "2018-04-04T14:14:40Z",
305
  "resolved_inferred": false,
306
  "started_at": "2026-04-23T18:48:46Z",
 
3
  "slug": "pipefy",
4
  "platform": "statuspage",
5
  "status_url": "https://status.pipefy.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "The incident was resolved",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-08-26T20:39:09Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-26T20:27:46Z",
 
24
  "body": "The incident was resolved after the domain was unblocked by the provider.",
25
  "first_seen": "2026-09-04T07:06:16Z",
26
  "impact": "minor",
27
+ "last_seen": "2026-09-04T14:19:03Z",
28
  "resolved_at": "2026-08-17T21:07:11Z",
29
  "resolved_inferred": false,
30
  "started_at": "2026-08-17T16:44:09Z",
 
36
  "body": "**Latest update**\nThe incident has been resolved following mitigation by the team",
37
  "first_seen": "2026-09-04T07:06:16Z",
38
  "impact": "minor",
39
+ "last_seen": "2026-09-04T14:19:03Z",
40
  "resolved_at": "2026-07-16T18:56:16Z",
41
  "resolved_inferred": false,
42
  "started_at": "2026-07-16T18:52:16Z",
 
48
  "body": "AI service Routing is working as expected and all AI services are back to normal.",
49
  "first_seen": "2026-09-04T07:06:16Z",
50
  "impact": "minor",
51
+ "last_seen": "2026-09-04T14:19:03Z",
52
  "resolved_at": "2026-07-08T22:16:37Z",
53
  "resolved_inferred": false,
54
  "started_at": "2026-07-08T20:24:43Z",
 
60
  "body": "The incident was resolved",
61
  "first_seen": "2026-09-04T07:06:16Z",
62
  "impact": "minor",
63
+ "last_seen": "2026-09-04T14:19:03Z",
64
  "resolved_at": "2026-06-15T20:46:36Z",
65
  "resolved_inferred": false,
66
  "started_at": "2026-06-15T20:45:34Z",
 
72
  "body": "The incident was resolved",
73
  "first_seen": "2026-09-04T07:06:16Z",
74
  "impact": "minor",
75
+ "last_seen": "2026-09-04T14:19:03Z",
76
  "resolved_at": "2026-06-15T20:23:48Z",
77
  "resolved_inferred": false,
78
  "started_at": "2026-06-15T20:07:21Z",
 
84
  "body": "The incident was resolved",
85
  "first_seen": "2026-09-04T07:06:16Z",
86
  "impact": "minor",
87
+ "last_seen": "2026-09-04T14:19:03Z",
88
  "resolved_at": "2026-06-03T20:47:24Z",
89
  "resolved_inferred": false,
90
  "started_at": "2026-06-03T20:38:50Z",
 
96
  "body": "This incident has been resolved.",
97
  "first_seen": "2026-09-04T07:06:16Z",
98
  "impact": "major",
99
+ "last_seen": "2026-09-04T14:19:03Z",
100
  "resolved_at": "2026-05-28T17:50:46Z",
101
  "resolved_inferred": false,
102
  "started_at": "2026-05-28T17:49:46Z",
 
108
  "body": "A fix was applied, and the incident was resolved.",
109
  "first_seen": "2026-09-04T07:06:16Z",
110
  "impact": "none",
111
+ "last_seen": "2026-09-04T14:19:03Z",
112
  "resolved_at": "2026-05-28T17:00:14Z",
113
  "resolved_inferred": false,
114
  "started_at": "2026-05-28T16:41:53Z",
 
120
  "body": "This incident has been resolved.",
121
  "first_seen": "2026-09-04T07:06:16Z",
122
  "impact": "minor",
123
+ "last_seen": "2026-09-04T14:19:03Z",
124
  "resolved_at": "2026-05-19T19:47:02Z",
125
  "resolved_inferred": false,
126
  "started_at": "2026-05-19T20:08:38Z",
 
132
  "body": "**Root Cause**\n\nThe issue was caused by an automation process that affected the system's performance. During this time, the speed of processing tasks was slower than usual, impacting the overall efficiency.\n\n**Resolution**\n\nThe problematic automation was removed, which restored the system's performance back to its normal state, ensuring that operations could continue smoothly.",
133
  "first_seen": "2026-09-04T07:06:16Z",
134
  "impact": "minor",
135
+ "last_seen": "2026-09-04T14:19:03Z",
136
  "resolved_at": "2026-05-13T21:51:03Z",
137
  "resolved_inferred": false,
138
  "started_at": "2026-05-13T21:08:41Z",
 
144
  "body": "**Root Cause**\n\nThe issue was traced back to a firmware update in a database instance, which led to a failure in the system's ability to switch over to a backup. This caused the main application to go down.\n\n**Resolution**\n\nThe problem was resolved by starting the database on a new healthy instance, restoring the system's functionality.\n\n**Action Plan**\n\n- To prevent future occurrences, a manual switch-over will be performed before any instance restarts. \n- Additionally, a maintenance is scheduled for the system update to address the identified bug.",
145
  "first_seen": "2026-09-04T07:06:16Z",
146
  "impact": "critical",
147
+ "last_seen": "2026-09-04T14:19:03Z",
148
  "resolved_at": "2026-05-08T22:59:56Z",
149
  "resolved_inferred": false,
150
  "started_at": "2026-05-08T23:06:26Z",
 
156
  "body": "This incident was resolved after a fix being implemented",
157
  "first_seen": "2026-09-04T07:06:16Z",
158
  "impact": "none",
159
+ "last_seen": "2026-09-04T14:19:03Z",
160
  "resolved_at": "2026-05-05T19:35:23Z",
161
  "resolved_inferred": false,
162
  "started_at": "2026-05-05T15:06:41Z",
 
168
  "body": "**Root Cause**\n\nThe application experienced performance issues due to a spike in executing flows that affected the app's performance. During the investigation, an issue was identified, requiring a fix to resolve the problem permanently.\n\n**Resolution**\n\nA fix to address the issue was implemented in the application, ensuring the application's performance returned to normal.\n\n**Action Plan**\n\nThe team will monitor new metrics in the scenario, to avoid the future impact",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "minor",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2026-05-04T19:48:21Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-05-04T19:06:34Z",
 
180
  "body": "Some new performance patches was applied during the monitoring period and we consider the incident resolved now.\r\nThe app performance is back to an expected level and all operations are running normally. \r\n\r\nWe apologize for the incident and the entire team evolved both technically and operationally to prevent this in the future.",
181
  "first_seen": "2026-09-04T07:06:16Z",
182
  "impact": "none",
183
+ "last_seen": "2026-09-04T14:19:03Z",
184
  "resolved_at": "2017-06-30T13:48:57Z",
185
  "resolved_inferred": false,
186
  "started_at": "2026-04-23T18:48:49Z",
 
192
  "body": "This incident has been resolved.",
193
  "first_seen": "2026-09-04T07:06:16Z",
194
  "impact": "none",
195
+ "last_seen": "2026-09-04T14:19:03Z",
196
  "resolved_at": "2017-10-13T18:16:23Z",
197
  "resolved_inferred": false,
198
  "started_at": "2026-04-23T18:48:48Z",
 
204
  "body": "All data is restored and reindexed again in our Elastic Search.\r\n\r\nWe are investigating whats happen in a post mortem meeting and find a better solution to prevent that it's happens again.",
205
  "first_seen": "2026-09-04T07:06:16Z",
206
  "impact": "none",
207
+ "last_seen": "2026-09-04T14:19:03Z",
208
  "resolved_at": "2017-10-09T22:51:49Z",
209
  "resolved_inferred": false,
210
  "started_at": "2026-04-23T18:48:48Z",
 
216
  "body": "This incident has been resolved.\r\n\r\nToday at 1:58 PM (UTC) our monitoring service identified a failure to communicate with the Redis database service responsible for background jobs.\r\n\r\nAt 2:00 PM (UTC) our team decided to put our disaster recovery in action, creating a new database that was finished successfully at 14:10 (UTC).\r\n\r\nOur automated test was run to check the overall status of the system. We've also put it online again for all users at 14:12 (UTC).",
217
  "first_seen": "2026-09-04T07:06:16Z",
218
  "impact": "none",
219
+ "last_seen": "2026-09-04T14:19:03Z",
220
  "resolved_at": "2017-09-04T14:26:00Z",
221
  "resolved_inferred": false,
222
  "started_at": "2026-04-23T18:48:48Z",
 
228
  "body": "This incident has been resolved.",
229
  "first_seen": "2026-09-04T07:06:16Z",
230
  "impact": "none",
231
+ "last_seen": "2026-09-04T14:19:03Z",
232
  "resolved_at": "2017-08-15T19:07:39Z",
233
  "resolved_inferred": false,
234
  "started_at": "2026-04-23T18:48:48Z",
 
240
  "body": "During a Redis migration our team identified a failure in HA, provided by our PaaS, which didn't run as expected.\r\nThat failure occurred between 0:14 AM and 0:17 AM (UTC) and was promptly handled by our Ops Team.",
241
  "first_seen": "2026-09-04T07:06:16Z",
242
  "impact": "none",
243
+ "last_seen": "2026-09-04T14:19:03Z",
244
  "resolved_at": "2018-03-16T00:14:00Z",
245
  "resolved_inferred": false,
246
  "started_at": "2026-04-23T18:48:47Z",
 
252
  "body": "This incident has been resolved.",
253
  "first_seen": "2026-09-04T07:06:16Z",
254
  "impact": "none",
255
+ "last_seen": "2026-09-04T14:19:03Z",
256
  "resolved_at": "2018-02-26T14:46:27Z",
257
  "resolved_inferred": false,
258
  "started_at": "2026-04-23T18:48:47Z",
 
264
  "body": "This incident has been resolved.",
265
  "first_seen": "2026-09-04T07:06:16Z",
266
  "impact": "none",
267
+ "last_seen": "2026-09-04T14:19:03Z",
268
  "resolved_at": "2018-01-19T20:46:00Z",
269
  "resolved_inferred": false,
270
  "started_at": "2026-04-23T18:48:47Z",
 
276
  "body": "The tests were successful and the system is working again.\r\n\r\nWe are working to improving this script so that this problem does not happen again.",
277
  "first_seen": "2026-09-04T07:06:16Z",
278
  "impact": "none",
279
+ "last_seen": "2026-09-04T14:19:03Z",
280
  "resolved_at": "2017-11-05T07:32:40Z",
281
  "resolved_inferred": false,
282
  "started_at": "2026-04-23T18:48:47Z",
 
288
  "body": "This incident has been resolved.",
289
  "first_seen": "2026-09-04T07:06:16Z",
290
  "impact": "none",
291
+ "last_seen": "2026-09-04T14:19:03Z",
292
  "resolved_at": "2017-10-16T20:34:29Z",
293
  "resolved_inferred": false,
294
  "started_at": "2026-04-23T18:48:47Z",
 
300
  "body": "We identify the problem, it happened because the gem [sequenced](https://github.com/derrickreimer/sequenced) that we use in our Ruby project locked the phase table, after that this process died and table stay locked.\r\n\r\nWe kill the process and restart the application that returns to respond as expected. Now we are removing that gem and move this logic to our database that can do this job in the same process and prevent this error.",
301
  "first_seen": "2026-09-04T07:06:16Z",
302
  "impact": "none",
303
+ "last_seen": "2026-09-04T14:19:03Z",
304
  "resolved_at": "2018-04-04T14:14:40Z",
305
  "resolved_inferred": false,
306
  "started_at": "2026-04-23T18:48:46Z",
api/v/plaid.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "plaid",
4
  "platform": "statuspage",
5
  "status_url": "https://status.plaid.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:16:22Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:16:22Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-08-24T21:13:11Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-24T05:36:33Z",
@@ -24,7 +24,7 @@
24
  "body": "The health issue with Navy Federal Credit Union has been resolved",
25
  "first_seen": "2026-09-04T07:16:22Z",
26
  "impact": "minor",
27
- "last_seen": "2026-09-04T12:24:18Z",
28
  "resolved_at": "2026-08-16T18:51:28Z",
29
  "resolved_inferred": false,
30
  "started_at": "2026-08-16T15:13:50Z",
@@ -36,7 +36,7 @@
36
  "body": "The Navy Federal Credit Union issue has been resolved",
37
  "first_seen": "2026-09-04T07:16:22Z",
38
  "impact": "none",
39
- "last_seen": "2026-09-04T12:24:18Z",
40
  "resolved_at": "2026-08-13T06:08:37Z",
41
  "resolved_inferred": false,
42
  "started_at": "2026-08-12T21:48:42Z",
@@ -48,7 +48,7 @@
48
  "body": "All Delayed Transactions have now been fully processed.",
49
  "first_seen": "2026-09-04T07:16:22Z",
50
  "impact": "none",
51
- "last_seen": "2026-09-04T12:24:18Z",
52
  "resolved_at": "2026-08-10T17:39:33Z",
53
  "resolved_inferred": false,
54
  "started_at": "2026-08-05T01:01:13Z",
@@ -60,7 +60,7 @@
60
  "body": "This incident has been resolved.",
61
  "first_seen": "2026-09-04T07:16:22Z",
62
  "impact": "major",
63
- "last_seen": "2026-09-04T12:24:18Z",
64
  "resolved_at": "2026-08-03T12:53:07Z",
65
  "resolved_inferred": false,
66
  "started_at": "2026-08-02T14:51:54Z",
@@ -72,7 +72,7 @@
72
  "body": "A fix is deployed. This incident has been resolved.",
73
  "first_seen": "2026-09-04T07:16:22Z",
74
  "impact": "minor",
75
- "last_seen": "2026-09-04T12:24:18Z",
76
  "resolved_at": "2026-08-01T02:56:39Z",
77
  "resolved_inferred": false,
78
  "started_at": "2026-08-01T01:34:19Z",
@@ -84,7 +84,7 @@
84
  "body": "This incident has been resolved. Our services have returned to normal operations.",
85
  "first_seen": "2026-09-04T07:16:22Z",
86
  "impact": "none",
87
- "last_seen": "2026-09-04T12:24:18Z",
88
  "resolved_at": "2026-07-28T08:40:32Z",
89
  "resolved_inferred": false,
90
  "started_at": "2026-07-27T16:34:08Z",
@@ -96,7 +96,7 @@
96
  "body": "All impacted ACH and Same-day ACH transfers's status have been updated to posted. They will be marked as settled later today.",
97
  "first_seen": "2026-09-04T07:16:22Z",
98
  "impact": "none",
99
- "last_seen": "2026-09-04T12:24:18Z",
100
  "resolved_at": "2026-07-23T21:59:09Z",
101
  "resolved_inferred": false,
102
  "started_at": "2026-07-23T20:36:48Z",
@@ -108,7 +108,7 @@
108
  "body": "This incident has been resolved.",
109
  "first_seen": "2026-09-04T07:16:22Z",
110
  "impact": "none",
111
- "last_seen": "2026-09-04T12:24:18Z",
112
  "resolved_at": "2026-07-23T14:33:08Z",
113
  "resolved_inferred": false,
114
  "started_at": "2026-07-23T11:41:04Z",
@@ -120,7 +120,7 @@
120
  "body": "This incident is now resolved. The underlying issue has been fully mitigated, and all delayed default update webhooks have now been delivered. New item connections and their initial and historical transaction webhooks are firing normally, and new transaction updates, including default update webhooks, are being processed normally.",
121
  "first_seen": "2026-09-04T07:16:22Z",
122
  "impact": "minor",
123
- "last_seen": "2026-09-04T12:24:18Z",
124
  "resolved_at": "2026-07-24T10:02:06Z",
125
  "resolved_inferred": false,
126
  "started_at": "2026-07-22T14:58:09Z",
@@ -132,7 +132,7 @@
132
  "body": "This incident has been resolved.",
133
  "first_seen": "2026-09-04T07:16:22Z",
134
  "impact": "none",
135
- "last_seen": "2026-09-04T12:24:18Z",
136
  "resolved_at": "2026-07-18T01:39:16Z",
137
  "resolved_inferred": false,
138
  "started_at": "2026-07-17T23:59:42Z",
@@ -144,7 +144,7 @@
144
  "body": "SSO and Google logins in the Plaid Dashboard are now performing as normal.",
145
  "first_seen": "2026-09-04T07:16:22Z",
146
  "impact": "major",
147
- "last_seen": "2026-09-04T12:24:18Z",
148
  "resolved_at": "2026-07-16T10:30:31Z",
149
  "resolved_inferred": false,
150
  "started_at": "2026-07-16T08:48:06Z",
@@ -156,7 +156,7 @@
156
  "body": "This incident has been resolved.",
157
  "first_seen": "2026-09-04T07:16:22Z",
158
  "impact": "none",
159
- "last_seen": "2026-09-04T12:24:18Z",
160
  "resolved_at": "2026-07-12T05:57:26Z",
161
  "resolved_inferred": false,
162
  "started_at": "2026-07-12T03:06:03Z",
@@ -168,7 +168,7 @@
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:16:22Z",
170
  "impact": "major",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2026-07-12T00:45:51Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-07-12T00:43:15Z",
@@ -180,7 +180,7 @@
180
  "body": "This incident has been resolved.",
181
  "first_seen": "2026-09-04T07:16:22Z",
182
  "impact": "major",
183
- "last_seen": "2026-09-04T12:24:18Z",
184
  "resolved_at": "2026-07-11T02:16:25Z",
185
  "resolved_inferred": false,
186
  "started_at": "2026-07-11T01:56:43Z",
@@ -192,7 +192,7 @@
192
  "body": "This incident has been resolved.",
193
  "first_seen": "2026-09-04T07:16:22Z",
194
  "impact": "none",
195
- "last_seen": "2026-09-04T12:24:18Z",
196
  "resolved_at": "2026-07-10T21:40:26Z",
197
  "resolved_inferred": false,
198
  "started_at": "2026-07-10T18:46:41Z",
@@ -204,7 +204,7 @@
204
  "body": "This incident has been resolved.",
205
  "first_seen": "2026-09-04T07:16:22Z",
206
  "impact": "minor",
207
- "last_seen": "2026-09-04T12:24:18Z",
208
  "resolved_at": "2026-07-10T21:38:25Z",
209
  "resolved_inferred": false,
210
  "started_at": "2026-07-10T16:51:44Z",
@@ -216,7 +216,7 @@
216
  "body": "This incident has been resolved.",
217
  "first_seen": "2026-09-04T07:16:22Z",
218
  "impact": "major",
219
- "last_seen": "2026-09-04T12:24:18Z",
220
  "resolved_at": "2026-07-10T19:23:26Z",
221
  "resolved_inferred": false,
222
  "started_at": "2026-07-10T16:04:57Z",
@@ -228,7 +228,7 @@
228
  "body": "This incident has been resolved.",
229
  "first_seen": "2026-09-04T07:16:22Z",
230
  "impact": "minor",
231
- "last_seen": "2026-09-04T12:24:18Z",
232
  "resolved_at": "2026-06-08T18:56:47Z",
233
  "resolved_inferred": false,
234
  "started_at": "2026-06-08T18:53:02Z",
@@ -240,7 +240,7 @@
240
  "body": "This incident has been resolved.",
241
  "first_seen": "2026-09-04T07:16:22Z",
242
  "impact": "major",
243
- "last_seen": "2026-09-04T12:24:18Z",
244
  "resolved_at": "2026-06-05T06:21:27Z",
245
  "resolved_inferred": false,
246
  "started_at": "2026-06-05T02:24:10Z",
@@ -252,7 +252,7 @@
252
  "body": "We experienced problems retrieving invoices on the Billing section of the Plaid dashboard between Thursday, May 21, 2026 12:00 PT - Tuesday, May 26, 2026 15:40 PT. This incident has been resolved.",
253
  "first_seen": "2026-09-04T07:16:22Z",
254
  "impact": "none",
255
- "last_seen": "2026-09-04T12:24:18Z",
256
  "resolved_at": "2026-05-26T23:00:00Z",
257
  "resolved_inferred": false,
258
  "started_at": "2026-05-26T23:13:00Z",
@@ -264,7 +264,7 @@
264
  "body": "This incident has been resolved.",
265
  "first_seen": "2026-09-04T07:16:22Z",
266
  "impact": "none",
267
- "last_seen": "2026-09-04T12:24:18Z",
268
  "resolved_at": "2026-05-27T00:02:06Z",
269
  "resolved_inferred": false,
270
  "started_at": "2026-05-26T22:42:22Z",
@@ -276,7 +276,7 @@
276
  "body": "This incident has been resolved.",
277
  "first_seen": "2026-09-04T07:16:22Z",
278
  "impact": "major",
279
- "last_seen": "2026-09-04T12:24:18Z",
280
  "resolved_at": "2026-05-26T22:42:00Z",
281
  "resolved_inferred": false,
282
  "started_at": "2026-05-26T22:33:42Z",
@@ -288,7 +288,7 @@
288
  "body": "This incident has been resolved.",
289
  "first_seen": "2026-09-04T07:16:22Z",
290
  "impact": "none",
291
- "last_seen": "2026-09-04T12:24:18Z",
292
  "resolved_at": "2026-05-22T00:30:25Z",
293
  "resolved_inferred": false,
294
  "started_at": "2026-05-21T19:36:51Z",
@@ -300,7 +300,7 @@
300
  "body": "This incident has been resolved.",
301
  "first_seen": "2026-09-04T07:16:22Z",
302
  "impact": "none",
303
- "last_seen": "2026-09-04T12:24:18Z",
304
  "resolved_at": "2026-05-22T00:30:41Z",
305
  "resolved_inferred": false,
306
  "started_at": "2026-05-21T19:33:23Z",
 
3
  "slug": "plaid",
4
  "platform": "statuspage",
5
  "status_url": "https://status.plaid.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:16:22Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:16:22Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-08-24T21:13:11Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-24T05:36:33Z",
 
24
  "body": "The health issue with Navy Federal Credit Union has been resolved",
25
  "first_seen": "2026-09-04T07:16:22Z",
26
  "impact": "minor",
27
+ "last_seen": "2026-09-04T14:19:03Z",
28
  "resolved_at": "2026-08-16T18:51:28Z",
29
  "resolved_inferred": false,
30
  "started_at": "2026-08-16T15:13:50Z",
 
36
  "body": "The Navy Federal Credit Union issue has been resolved",
37
  "first_seen": "2026-09-04T07:16:22Z",
38
  "impact": "none",
39
+ "last_seen": "2026-09-04T14:19:03Z",
40
  "resolved_at": "2026-08-13T06:08:37Z",
41
  "resolved_inferred": false,
42
  "started_at": "2026-08-12T21:48:42Z",
 
48
  "body": "All Delayed Transactions have now been fully processed.",
49
  "first_seen": "2026-09-04T07:16:22Z",
50
  "impact": "none",
51
+ "last_seen": "2026-09-04T14:19:03Z",
52
  "resolved_at": "2026-08-10T17:39:33Z",
53
  "resolved_inferred": false,
54
  "started_at": "2026-08-05T01:01:13Z",
 
60
  "body": "This incident has been resolved.",
61
  "first_seen": "2026-09-04T07:16:22Z",
62
  "impact": "major",
63
+ "last_seen": "2026-09-04T14:19:03Z",
64
  "resolved_at": "2026-08-03T12:53:07Z",
65
  "resolved_inferred": false,
66
  "started_at": "2026-08-02T14:51:54Z",
 
72
  "body": "A fix is deployed. This incident has been resolved.",
73
  "first_seen": "2026-09-04T07:16:22Z",
74
  "impact": "minor",
75
+ "last_seen": "2026-09-04T14:19:03Z",
76
  "resolved_at": "2026-08-01T02:56:39Z",
77
  "resolved_inferred": false,
78
  "started_at": "2026-08-01T01:34:19Z",
 
84
  "body": "This incident has been resolved. Our services have returned to normal operations.",
85
  "first_seen": "2026-09-04T07:16:22Z",
86
  "impact": "none",
87
+ "last_seen": "2026-09-04T14:19:03Z",
88
  "resolved_at": "2026-07-28T08:40:32Z",
89
  "resolved_inferred": false,
90
  "started_at": "2026-07-27T16:34:08Z",
 
96
  "body": "All impacted ACH and Same-day ACH transfers's status have been updated to posted. They will be marked as settled later today.",
97
  "first_seen": "2026-09-04T07:16:22Z",
98
  "impact": "none",
99
+ "last_seen": "2026-09-04T14:19:03Z",
100
  "resolved_at": "2026-07-23T21:59:09Z",
101
  "resolved_inferred": false,
102
  "started_at": "2026-07-23T20:36:48Z",
 
108
  "body": "This incident has been resolved.",
109
  "first_seen": "2026-09-04T07:16:22Z",
110
  "impact": "none",
111
+ "last_seen": "2026-09-04T14:19:03Z",
112
  "resolved_at": "2026-07-23T14:33:08Z",
113
  "resolved_inferred": false,
114
  "started_at": "2026-07-23T11:41:04Z",
 
120
  "body": "This incident is now resolved. The underlying issue has been fully mitigated, and all delayed default update webhooks have now been delivered. New item connections and their initial and historical transaction webhooks are firing normally, and new transaction updates, including default update webhooks, are being processed normally.",
121
  "first_seen": "2026-09-04T07:16:22Z",
122
  "impact": "minor",
123
+ "last_seen": "2026-09-04T14:19:03Z",
124
  "resolved_at": "2026-07-24T10:02:06Z",
125
  "resolved_inferred": false,
126
  "started_at": "2026-07-22T14:58:09Z",
 
132
  "body": "This incident has been resolved.",
133
  "first_seen": "2026-09-04T07:16:22Z",
134
  "impact": "none",
135
+ "last_seen": "2026-09-04T14:19:03Z",
136
  "resolved_at": "2026-07-18T01:39:16Z",
137
  "resolved_inferred": false,
138
  "started_at": "2026-07-17T23:59:42Z",
 
144
  "body": "SSO and Google logins in the Plaid Dashboard are now performing as normal.",
145
  "first_seen": "2026-09-04T07:16:22Z",
146
  "impact": "major",
147
+ "last_seen": "2026-09-04T14:19:03Z",
148
  "resolved_at": "2026-07-16T10:30:31Z",
149
  "resolved_inferred": false,
150
  "started_at": "2026-07-16T08:48:06Z",
 
156
  "body": "This incident has been resolved.",
157
  "first_seen": "2026-09-04T07:16:22Z",
158
  "impact": "none",
159
+ "last_seen": "2026-09-04T14:19:03Z",
160
  "resolved_at": "2026-07-12T05:57:26Z",
161
  "resolved_inferred": false,
162
  "started_at": "2026-07-12T03:06:03Z",
 
168
  "body": "This incident has been resolved.",
169
  "first_seen": "2026-09-04T07:16:22Z",
170
  "impact": "major",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2026-07-12T00:45:51Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-07-12T00:43:15Z",
 
180
  "body": "This incident has been resolved.",
181
  "first_seen": "2026-09-04T07:16:22Z",
182
  "impact": "major",
183
+ "last_seen": "2026-09-04T14:19:03Z",
184
  "resolved_at": "2026-07-11T02:16:25Z",
185
  "resolved_inferred": false,
186
  "started_at": "2026-07-11T01:56:43Z",
 
192
  "body": "This incident has been resolved.",
193
  "first_seen": "2026-09-04T07:16:22Z",
194
  "impact": "none",
195
+ "last_seen": "2026-09-04T14:19:03Z",
196
  "resolved_at": "2026-07-10T21:40:26Z",
197
  "resolved_inferred": false,
198
  "started_at": "2026-07-10T18:46:41Z",
 
204
  "body": "This incident has been resolved.",
205
  "first_seen": "2026-09-04T07:16:22Z",
206
  "impact": "minor",
207
+ "last_seen": "2026-09-04T14:19:03Z",
208
  "resolved_at": "2026-07-10T21:38:25Z",
209
  "resolved_inferred": false,
210
  "started_at": "2026-07-10T16:51:44Z",
 
216
  "body": "This incident has been resolved.",
217
  "first_seen": "2026-09-04T07:16:22Z",
218
  "impact": "major",
219
+ "last_seen": "2026-09-04T14:19:03Z",
220
  "resolved_at": "2026-07-10T19:23:26Z",
221
  "resolved_inferred": false,
222
  "started_at": "2026-07-10T16:04:57Z",
 
228
  "body": "This incident has been resolved.",
229
  "first_seen": "2026-09-04T07:16:22Z",
230
  "impact": "minor",
231
+ "last_seen": "2026-09-04T14:19:03Z",
232
  "resolved_at": "2026-06-08T18:56:47Z",
233
  "resolved_inferred": false,
234
  "started_at": "2026-06-08T18:53:02Z",
 
240
  "body": "This incident has been resolved.",
241
  "first_seen": "2026-09-04T07:16:22Z",
242
  "impact": "major",
243
+ "last_seen": "2026-09-04T14:19:03Z",
244
  "resolved_at": "2026-06-05T06:21:27Z",
245
  "resolved_inferred": false,
246
  "started_at": "2026-06-05T02:24:10Z",
 
252
  "body": "We experienced problems retrieving invoices on the Billing section of the Plaid dashboard between Thursday, May 21, 2026 12:00 PT - Tuesday, May 26, 2026 15:40 PT. This incident has been resolved.",
253
  "first_seen": "2026-09-04T07:16:22Z",
254
  "impact": "none",
255
+ "last_seen": "2026-09-04T14:19:03Z",
256
  "resolved_at": "2026-05-26T23:00:00Z",
257
  "resolved_inferred": false,
258
  "started_at": "2026-05-26T23:13:00Z",
 
264
  "body": "This incident has been resolved.",
265
  "first_seen": "2026-09-04T07:16:22Z",
266
  "impact": "none",
267
+ "last_seen": "2026-09-04T14:19:03Z",
268
  "resolved_at": "2026-05-27T00:02:06Z",
269
  "resolved_inferred": false,
270
  "started_at": "2026-05-26T22:42:22Z",
 
276
  "body": "This incident has been resolved.",
277
  "first_seen": "2026-09-04T07:16:22Z",
278
  "impact": "major",
279
+ "last_seen": "2026-09-04T14:19:03Z",
280
  "resolved_at": "2026-05-26T22:42:00Z",
281
  "resolved_inferred": false,
282
  "started_at": "2026-05-26T22:33:42Z",
 
288
  "body": "This incident has been resolved.",
289
  "first_seen": "2026-09-04T07:16:22Z",
290
  "impact": "none",
291
+ "last_seen": "2026-09-04T14:19:03Z",
292
  "resolved_at": "2026-05-22T00:30:25Z",
293
  "resolved_inferred": false,
294
  "started_at": "2026-05-21T19:36:51Z",
 
300
  "body": "This incident has been resolved.",
301
  "first_seen": "2026-09-04T07:16:22Z",
302
  "impact": "none",
303
+ "last_seen": "2026-09-04T14:19:03Z",
304
  "resolved_at": "2026-05-22T00:30:41Z",
305
  "resolved_inferred": false,
306
  "started_at": "2026-05-21T19:33:23Z",
api/v/planetscale.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "planetscale",
4
  "platform": "statuspage",
5
  "status_url": "https://www.planetscalestatus.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "The incident has been resolved. Between 12:17 and 12:24 UTC, the dashboard and API were returning 500 errors for postgres database management pages and API endpoints.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-09-02T16:44:27Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-02T16:34:16Z",
@@ -24,7 +24,7 @@
24
  "body": "The incident has been resolved.",
25
  "first_seen": "2026-09-04T07:06:16Z",
26
  "impact": "major",
27
- "last_seen": "2026-09-04T12:24:18Z",
28
  "resolved_at": "2026-07-24T17:42:00Z",
29
  "resolved_inferred": false,
30
  "started_at": "2026-07-24T14:41:44Z",
@@ -36,7 +36,7 @@
36
  "body": "Query Insights functionality is restored on all Postgres development branches. ",
37
  "first_seen": "2026-09-04T07:06:16Z",
38
  "impact": "minor",
39
- "last_seen": "2026-09-04T12:24:18Z",
40
  "resolved_at": "2026-07-21T15:18:54Z",
41
  "resolved_inferred": false,
42
  "started_at": "2026-07-20T18:29:38Z",
@@ -48,7 +48,7 @@
48
  "body": "Connection issues have been resolved. If you experience any further issues, please contact our support team.",
49
  "first_seen": "2026-09-04T07:06:16Z",
50
  "impact": "major",
51
- "last_seen": "2026-09-04T12:24:18Z",
52
  "resolved_at": "2026-07-18T21:05:31Z",
53
  "resolved_inferred": false,
54
  "started_at": "2026-07-18T20:32:44Z",
@@ -60,7 +60,7 @@
60
  "body": "API and dashboard service is restored.",
61
  "first_seen": "2026-09-04T07:06:16Z",
62
  "impact": "major",
63
- "last_seen": "2026-09-04T12:24:18Z",
64
  "resolved_at": "2026-07-17T17:09:28Z",
65
  "resolved_inferred": false,
66
  "started_at": "2026-07-17T16:41:49Z",
@@ -72,7 +72,7 @@
72
  "body": "The issue is resolved. SSO is working fine again.",
73
  "first_seen": "2026-09-04T07:06:16Z",
74
  "impact": "minor",
75
- "last_seen": "2026-09-04T12:24:18Z",
76
  "resolved_at": "2026-07-16T10:52:14Z",
77
  "resolved_inferred": false,
78
  "started_at": "2026-07-16T09:30:45Z",
@@ -84,7 +84,7 @@
84
  "body": "All impacted branches are recovered.\n\nPlanetScale upgraded development Vitess branches with Vectors enabled from MySQL 8.0.x to 8.4.x. PlanetScale runs an internal fork containing support for PlanetScale's MySQL Vectors indexes. \n\nA bug in the 8.4.x version of our Vectors builds resulted in the upgrade immediately failing on startup.\n\nBecause Vitess development branches only have one instance - the primary - impacted development branches did not have a primary during the impact window.\n\nThe incident was resolved by reverting impacted branches to their previous MySQL version.\n\nPlanetScale will fix the bug in the MySQL Vectors 8.4.x build before re-attempting the upgrade at a later date.",
85
  "first_seen": "2026-09-04T07:06:16Z",
86
  "impact": "minor",
87
- "last_seen": "2026-09-04T12:24:18Z",
88
  "resolved_at": "2026-07-06T21:45:07Z",
89
  "resolved_inferred": false,
90
  "started_at": "2026-07-06T19:18:34Z",
@@ -96,7 +96,7 @@
96
  "body": "The changes we applied are effectively preventing further unexpected restarts to the high availability component shared by Postgres clusters. We have not seen further restarts to this component nor unplanned failovers in Postgres clusters since applying these changes. ",
97
  "first_seen": "2026-09-04T07:06:16Z",
98
  "impact": "major",
99
- "last_seen": "2026-09-04T12:24:18Z",
100
  "resolved_at": "2026-05-14T21:03:14Z",
101
  "resolved_inferred": false,
102
  "started_at": "2026-05-14T20:30:55Z",
@@ -108,7 +108,7 @@
108
  "body": "PlanetScale has remediated the issue and it is fully resolved.",
109
  "first_seen": "2026-09-04T07:06:16Z",
110
  "impact": "minor",
111
- "last_seen": "2026-09-04T12:24:18Z",
112
  "resolved_at": "2026-05-13T18:04:37Z",
113
  "resolved_inferred": false,
114
  "started_at": "2026-05-13T17:17:04Z",
@@ -120,7 +120,7 @@
120
  "body": "PlanetScale is not observing any database impact resulting from the AWS use1-az4 thermal event. Please contact support if you have any questions or notice any disruption.",
121
  "first_seen": "2026-09-04T07:06:16Z",
122
  "impact": "none",
123
- "last_seen": "2026-09-04T12:24:18Z",
124
  "resolved_at": "2026-05-08T19:22:11Z",
125
  "resolved_inferred": false,
126
  "started_at": "2026-05-08T02:22:38Z",
@@ -132,7 +132,7 @@
132
  "body": "The errors have been resolved.",
133
  "first_seen": "2026-09-04T07:06:16Z",
134
  "impact": "minor",
135
- "last_seen": "2026-09-04T12:24:18Z",
136
  "resolved_at": "2026-04-08T00:49:49Z",
137
  "resolved_inferred": false,
138
  "started_at": "2026-04-08T00:34:35Z",
@@ -144,7 +144,7 @@
144
  "body": "Some percentage of new credential creates, updates, and deletes errored or were very slow for approx 35 minutes.",
145
  "first_seen": "2026-09-04T07:06:16Z",
146
  "impact": "minor",
147
- "last_seen": "2026-09-04T12:24:18Z",
148
  "resolved_at": "2026-04-02T22:52:31Z",
149
  "resolved_inferred": false,
150
  "started_at": "2026-04-02T22:37:39Z",
@@ -156,7 +156,7 @@
156
  "body": "This incident has been resolved.",
157
  "first_seen": "2026-09-04T07:06:16Z",
158
  "impact": "major",
159
- "last_seen": "2026-09-04T12:24:18Z",
160
  "resolved_at": "2026-03-11T13:19:06Z",
161
  "resolved_inferred": false,
162
  "started_at": "2026-03-11T13:04:02Z",
@@ -168,7 +168,7 @@
168
  "body": "Vitess branch creation is available once again.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2026-02-24T12:00:30Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-02-24T10:26:20Z",
@@ -180,7 +180,7 @@
180
  "body": "Problem has been resolved. We saw three nodes fail across three availability zones simultaneously. Impacting databases hosted on those nodes.\n\nAll databases have been moved to healthy nodes and we're investigating how we can further reduce impact from similar events in the future.",
181
  "first_seen": "2026-09-04T07:06:16Z",
182
  "impact": "major",
183
- "last_seen": "2026-09-04T12:24:18Z",
184
  "resolved_at": "2026-02-18T21:06:29Z",
185
  "resolved_inferred": false,
186
  "started_at": "2026-02-18T20:23:32Z",
@@ -192,7 +192,7 @@
192
  "body": "Query Insights is fully operational.",
193
  "first_seen": "2026-09-04T07:06:16Z",
194
  "impact": "critical",
195
- "last_seen": "2026-09-04T12:24:18Z",
196
  "resolved_at": "2026-01-31T11:58:04Z",
197
  "resolved_inferred": false,
198
  "started_at": "2026-01-31T09:38:50Z",
@@ -204,7 +204,7 @@
204
  "body": "The issue has been resolved.",
205
  "first_seen": "2026-09-04T07:06:16Z",
206
  "impact": "major",
207
- "last_seen": "2026-09-04T12:24:18Z",
208
  "resolved_at": "2026-01-09T01:46:16Z",
209
  "resolved_inferred": false,
210
  "started_at": "2026-01-09T01:29:20Z",
@@ -216,7 +216,7 @@
216
  "body": "Insights data ingestion encountered an error due to an unexpected data format. The issue was identified and fixed, and ingestion resumed.",
217
  "first_seen": "2026-09-04T07:06:16Z",
218
  "impact": "minor",
219
- "last_seen": "2026-09-04T12:24:18Z",
220
  "resolved_at": "2026-01-08T18:14:46Z",
221
  "resolved_inferred": false,
222
  "started_at": "2026-01-08T16:30:19Z",
@@ -228,7 +228,7 @@
228
  "body": "This incident is resolved.",
229
  "first_seen": "2026-09-04T07:06:16Z",
230
  "impact": "major",
231
- "last_seen": "2026-09-04T12:24:18Z",
232
  "resolved_at": "2026-01-06T17:41:21Z",
233
  "resolved_inferred": false,
234
  "started_at": "2026-01-06T16:27:46Z",
@@ -240,7 +240,7 @@
240
  "body": "We've made a fix and the errors have resolved.",
241
  "first_seen": "2026-09-04T07:06:16Z",
242
  "impact": "major",
243
- "last_seen": "2026-09-04T12:24:18Z",
244
  "resolved_at": "2025-11-13T18:45:00Z",
245
  "resolved_inferred": false,
246
  "started_at": "2025-11-17T18:10:21Z",
@@ -252,7 +252,7 @@
252
  "body": "Datadog metrics are back up-to-date.",
253
  "first_seen": "2026-09-04T07:06:16Z",
254
  "impact": "minor",
255
- "last_seen": "2026-09-04T12:24:18Z",
256
  "resolved_at": "2025-10-20T16:36:39Z",
257
  "resolved_inferred": false,
258
  "started_at": "2025-10-20T16:09:10Z",
@@ -264,7 +264,7 @@
264
  "body": "PlanetScale is continuing to monitor the condition of AWS us-east-1. At this point we do not see any further impact, and have re-enabled database and branch creation in the region. ",
265
  "first_seen": "2026-09-04T07:06:16Z",
266
  "impact": "minor",
267
- "last_seen": "2026-09-04T12:24:18Z",
268
  "resolved_at": "2025-10-20T09:36:00Z",
269
  "resolved_inferred": false,
270
  "started_at": "2025-10-20T09:53:18Z",
@@ -276,7 +276,7 @@
276
  "body": "No further disruption is expected, please contact support with any further issues.",
277
  "first_seen": "2026-09-04T07:06:16Z",
278
  "impact": "major",
279
- "last_seen": "2026-09-04T12:24:18Z",
280
  "resolved_at": "2025-10-16T01:52:52Z",
281
  "resolved_inferred": false,
282
  "started_at": "2025-10-15T18:29:33Z",
@@ -288,7 +288,7 @@
288
  "body": "We've resolved the issue. SSO/SAML is working again.",
289
  "first_seen": "2026-09-04T07:06:16Z",
290
  "impact": "major",
291
- "last_seen": "2026-09-04T12:24:18Z",
292
  "resolved_at": "2025-10-07T23:12:01Z",
293
  "resolved_inferred": false,
294
  "started_at": "2025-10-07T22:04:12Z",
@@ -300,7 +300,7 @@
300
  "body": "All systems operating normally",
301
  "first_seen": "2026-09-04T07:06:16Z",
302
  "impact": "minor",
303
- "last_seen": "2026-09-04T12:24:18Z",
304
  "resolved_at": "2025-10-01T15:15:11Z",
305
  "resolved_inferred": false,
306
  "started_at": "2025-10-01T15:10:50Z",
 
3
  "slug": "planetscale",
4
  "platform": "statuspage",
5
  "status_url": "https://www.planetscalestatus.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "The incident has been resolved. Between 12:17 and 12:24 UTC, the dashboard and API were returning 500 errors for postgres database management pages and API endpoints.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-09-02T16:44:27Z",
17
  "resolved_inferred": false,
18
  "started_at": "2026-09-02T16:34:16Z",
 
24
  "body": "The incident has been resolved.",
25
  "first_seen": "2026-09-04T07:06:16Z",
26
  "impact": "major",
27
+ "last_seen": "2026-09-04T14:19:03Z",
28
  "resolved_at": "2026-07-24T17:42:00Z",
29
  "resolved_inferred": false,
30
  "started_at": "2026-07-24T14:41:44Z",
 
36
  "body": "Query Insights functionality is restored on all Postgres development branches. ",
37
  "first_seen": "2026-09-04T07:06:16Z",
38
  "impact": "minor",
39
+ "last_seen": "2026-09-04T14:19:03Z",
40
  "resolved_at": "2026-07-21T15:18:54Z",
41
  "resolved_inferred": false,
42
  "started_at": "2026-07-20T18:29:38Z",
 
48
  "body": "Connection issues have been resolved. If you experience any further issues, please contact our support team.",
49
  "first_seen": "2026-09-04T07:06:16Z",
50
  "impact": "major",
51
+ "last_seen": "2026-09-04T14:19:03Z",
52
  "resolved_at": "2026-07-18T21:05:31Z",
53
  "resolved_inferred": false,
54
  "started_at": "2026-07-18T20:32:44Z",
 
60
  "body": "API and dashboard service is restored.",
61
  "first_seen": "2026-09-04T07:06:16Z",
62
  "impact": "major",
63
+ "last_seen": "2026-09-04T14:19:03Z",
64
  "resolved_at": "2026-07-17T17:09:28Z",
65
  "resolved_inferred": false,
66
  "started_at": "2026-07-17T16:41:49Z",
 
72
  "body": "The issue is resolved. SSO is working fine again.",
73
  "first_seen": "2026-09-04T07:06:16Z",
74
  "impact": "minor",
75
+ "last_seen": "2026-09-04T14:19:03Z",
76
  "resolved_at": "2026-07-16T10:52:14Z",
77
  "resolved_inferred": false,
78
  "started_at": "2026-07-16T09:30:45Z",
 
84
  "body": "All impacted branches are recovered.\n\nPlanetScale upgraded development Vitess branches with Vectors enabled from MySQL 8.0.x to 8.4.x. PlanetScale runs an internal fork containing support for PlanetScale's MySQL Vectors indexes. \n\nA bug in the 8.4.x version of our Vectors builds resulted in the upgrade immediately failing on startup.\n\nBecause Vitess development branches only have one instance - the primary - impacted development branches did not have a primary during the impact window.\n\nThe incident was resolved by reverting impacted branches to their previous MySQL version.\n\nPlanetScale will fix the bug in the MySQL Vectors 8.4.x build before re-attempting the upgrade at a later date.",
85
  "first_seen": "2026-09-04T07:06:16Z",
86
  "impact": "minor",
87
+ "last_seen": "2026-09-04T14:19:03Z",
88
  "resolved_at": "2026-07-06T21:45:07Z",
89
  "resolved_inferred": false,
90
  "started_at": "2026-07-06T19:18:34Z",
 
96
  "body": "The changes we applied are effectively preventing further unexpected restarts to the high availability component shared by Postgres clusters. We have not seen further restarts to this component nor unplanned failovers in Postgres clusters since applying these changes. ",
97
  "first_seen": "2026-09-04T07:06:16Z",
98
  "impact": "major",
99
+ "last_seen": "2026-09-04T14:19:03Z",
100
  "resolved_at": "2026-05-14T21:03:14Z",
101
  "resolved_inferred": false,
102
  "started_at": "2026-05-14T20:30:55Z",
 
108
  "body": "PlanetScale has remediated the issue and it is fully resolved.",
109
  "first_seen": "2026-09-04T07:06:16Z",
110
  "impact": "minor",
111
+ "last_seen": "2026-09-04T14:19:03Z",
112
  "resolved_at": "2026-05-13T18:04:37Z",
113
  "resolved_inferred": false,
114
  "started_at": "2026-05-13T17:17:04Z",
 
120
  "body": "PlanetScale is not observing any database impact resulting from the AWS use1-az4 thermal event. Please contact support if you have any questions or notice any disruption.",
121
  "first_seen": "2026-09-04T07:06:16Z",
122
  "impact": "none",
123
+ "last_seen": "2026-09-04T14:19:03Z",
124
  "resolved_at": "2026-05-08T19:22:11Z",
125
  "resolved_inferred": false,
126
  "started_at": "2026-05-08T02:22:38Z",
 
132
  "body": "The errors have been resolved.",
133
  "first_seen": "2026-09-04T07:06:16Z",
134
  "impact": "minor",
135
+ "last_seen": "2026-09-04T14:19:03Z",
136
  "resolved_at": "2026-04-08T00:49:49Z",
137
  "resolved_inferred": false,
138
  "started_at": "2026-04-08T00:34:35Z",
 
144
  "body": "Some percentage of new credential creates, updates, and deletes errored or were very slow for approx 35 minutes.",
145
  "first_seen": "2026-09-04T07:06:16Z",
146
  "impact": "minor",
147
+ "last_seen": "2026-09-04T14:19:03Z",
148
  "resolved_at": "2026-04-02T22:52:31Z",
149
  "resolved_inferred": false,
150
  "started_at": "2026-04-02T22:37:39Z",
 
156
  "body": "This incident has been resolved.",
157
  "first_seen": "2026-09-04T07:06:16Z",
158
  "impact": "major",
159
+ "last_seen": "2026-09-04T14:19:03Z",
160
  "resolved_at": "2026-03-11T13:19:06Z",
161
  "resolved_inferred": false,
162
  "started_at": "2026-03-11T13:04:02Z",
 
168
  "body": "Vitess branch creation is available once again.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "major",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2026-02-24T12:00:30Z",
173
  "resolved_inferred": false,
174
  "started_at": "2026-02-24T10:26:20Z",
 
180
  "body": "Problem has been resolved. We saw three nodes fail across three availability zones simultaneously. Impacting databases hosted on those nodes.\n\nAll databases have been moved to healthy nodes and we're investigating how we can further reduce impact from similar events in the future.",
181
  "first_seen": "2026-09-04T07:06:16Z",
182
  "impact": "major",
183
+ "last_seen": "2026-09-04T14:19:03Z",
184
  "resolved_at": "2026-02-18T21:06:29Z",
185
  "resolved_inferred": false,
186
  "started_at": "2026-02-18T20:23:32Z",
 
192
  "body": "Query Insights is fully operational.",
193
  "first_seen": "2026-09-04T07:06:16Z",
194
  "impact": "critical",
195
+ "last_seen": "2026-09-04T14:19:03Z",
196
  "resolved_at": "2026-01-31T11:58:04Z",
197
  "resolved_inferred": false,
198
  "started_at": "2026-01-31T09:38:50Z",
 
204
  "body": "The issue has been resolved.",
205
  "first_seen": "2026-09-04T07:06:16Z",
206
  "impact": "major",
207
+ "last_seen": "2026-09-04T14:19:03Z",
208
  "resolved_at": "2026-01-09T01:46:16Z",
209
  "resolved_inferred": false,
210
  "started_at": "2026-01-09T01:29:20Z",
 
216
  "body": "Insights data ingestion encountered an error due to an unexpected data format. The issue was identified and fixed, and ingestion resumed.",
217
  "first_seen": "2026-09-04T07:06:16Z",
218
  "impact": "minor",
219
+ "last_seen": "2026-09-04T14:19:03Z",
220
  "resolved_at": "2026-01-08T18:14:46Z",
221
  "resolved_inferred": false,
222
  "started_at": "2026-01-08T16:30:19Z",
 
228
  "body": "This incident is resolved.",
229
  "first_seen": "2026-09-04T07:06:16Z",
230
  "impact": "major",
231
+ "last_seen": "2026-09-04T14:19:03Z",
232
  "resolved_at": "2026-01-06T17:41:21Z",
233
  "resolved_inferred": false,
234
  "started_at": "2026-01-06T16:27:46Z",
 
240
  "body": "We've made a fix and the errors have resolved.",
241
  "first_seen": "2026-09-04T07:06:16Z",
242
  "impact": "major",
243
+ "last_seen": "2026-09-04T14:19:03Z",
244
  "resolved_at": "2025-11-13T18:45:00Z",
245
  "resolved_inferred": false,
246
  "started_at": "2025-11-17T18:10:21Z",
 
252
  "body": "Datadog metrics are back up-to-date.",
253
  "first_seen": "2026-09-04T07:06:16Z",
254
  "impact": "minor",
255
+ "last_seen": "2026-09-04T14:19:03Z",
256
  "resolved_at": "2025-10-20T16:36:39Z",
257
  "resolved_inferred": false,
258
  "started_at": "2025-10-20T16:09:10Z",
 
264
  "body": "PlanetScale is continuing to monitor the condition of AWS us-east-1. At this point we do not see any further impact, and have re-enabled database and branch creation in the region. ",
265
  "first_seen": "2026-09-04T07:06:16Z",
266
  "impact": "minor",
267
+ "last_seen": "2026-09-04T14:19:03Z",
268
  "resolved_at": "2025-10-20T09:36:00Z",
269
  "resolved_inferred": false,
270
  "started_at": "2025-10-20T09:53:18Z",
 
276
  "body": "No further disruption is expected, please contact support with any further issues.",
277
  "first_seen": "2026-09-04T07:06:16Z",
278
  "impact": "major",
279
+ "last_seen": "2026-09-04T14:19:03Z",
280
  "resolved_at": "2025-10-16T01:52:52Z",
281
  "resolved_inferred": false,
282
  "started_at": "2025-10-15T18:29:33Z",
 
288
  "body": "We've resolved the issue. SSO/SAML is working again.",
289
  "first_seen": "2026-09-04T07:06:16Z",
290
  "impact": "major",
291
+ "last_seen": "2026-09-04T14:19:03Z",
292
  "resolved_at": "2025-10-07T23:12:01Z",
293
  "resolved_inferred": false,
294
  "started_at": "2025-10-07T22:04:12Z",
 
300
  "body": "All systems operating normally",
301
  "first_seen": "2026-09-04T07:06:16Z",
302
  "impact": "minor",
303
+ "last_seen": "2026-09-04T14:19:03Z",
304
  "resolved_at": "2025-10-01T15:15:11Z",
305
  "resolved_inferred": false,
306
  "started_at": "2025-10-01T15:10:50Z",
api/v/platform9.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "platform9",
4
  "platform": "statuspage",
5
  "status_url": "https://status.platform9.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "none",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-07-24T06:06:13.058-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-07-24T05:50:56.499-07:00",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-04-23T05:14:47.355-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-04-22T22:56:30.919-07:00",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "critical",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2025-09-29T22:14:20.951-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2025-09-28T11:00:18.000-07:00",
 
3
  "slug": "platform9",
4
  "platform": "statuspage",
5
  "status_url": "https://status.platform9.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "none",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-07-24T06:06:13.058-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-07-24T05:50:56.499-07:00",
 
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "major",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-04-23T05:14:47.355-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-04-22T22:56:30.919-07:00",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "critical",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2025-09-29T22:14:20.951-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2025-09-28T11:00:18.000-07:00",
api/v/playfab.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "playfab",
4
  "platform": "statuspage",
5
  "status_url": "https://status.playfab.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-08-27T18:34:07.423-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-27T11:12:17.933-07:00",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "none",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2026-08-23T15:34:54.831-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-23T08:42:44.852-07:00",
@@ -38,7 +38,7 @@
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "major",
41
- "last_seen": "2026-09-04T12:24:18Z",
42
  "resolved_at": "2026-08-07T21:09:06.038-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-08-07T10:47:54.381-07:00",
@@ -51,7 +51,7 @@
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
- "last_seen": "2026-09-04T12:24:18Z",
55
  "resolved_at": "2026-07-23T12:01:47.891-07:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-07-23T09:11:33.782-07:00",
@@ -64,7 +64,7 @@
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "major",
67
- "last_seen": "2026-09-04T12:24:18Z",
68
  "resolved_at": "2026-07-21T08:24:00.219-07:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-07-16T14:37:44.991-07:00",
@@ -77,7 +77,7 @@
77
  "body": "The incident is now resolved",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "none",
80
- "last_seen": "2026-09-04T12:24:18Z",
81
  "resolved_at": "2026-07-02T13:05:51.346-07:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-07-02T12:32:14.608-07:00",
@@ -90,7 +90,7 @@
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "none",
93
- "last_seen": "2026-09-04T12:24:18Z",
94
  "resolved_at": "2026-06-23T19:52:29.691-07:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-06-23T18:02:09.014-07:00",
@@ -103,7 +103,7 @@
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
- "last_seen": "2026-09-04T12:24:18Z",
107
  "resolved_at": "2026-06-16T13:14:31.380-07:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-06-12T13:51:24.295-07:00",
@@ -116,7 +116,7 @@
116
  "body": "Some APIs temporarily received HTTP 429 errors.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "none",
119
- "last_seen": "2026-09-04T12:24:18Z",
120
  "resolved_at": "2026-06-08T08:30:00.000-07:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-06-08T08:30:00.000-07:00",
@@ -129,7 +129,7 @@
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
- "last_seen": "2026-09-04T12:24:18Z",
133
  "resolved_at": "2026-06-19T09:12:31.000-07:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-05-30T13:33:06.122-07:00",
@@ -142,7 +142,7 @@
142
  "body": "On May 29, 2026, between approximately 9:00 PM and 10:09 PM Pacific Time, some customers experienced increased failures and timeouts across multiple PlayFab APIs. The issue was caused by an upstream infrastructure outage in the hosting environment that disrupted connectivity to backend storage services. The issue auto-resolved once the upstream infrastructure problem was mitigated.\u00a0\n\n### Impact\u00a0\n\nDuring the impact window, customers experienced elevated error rates, timeouts, and connection disruptions when calling PlayFab APIs. Services including Lobby, Matchmaking, and real-time messaging were most heavily affected, with availability for those services degraded to between 75% and 95%. Multiple titles were impacted during the approximately 26-minute incident window.\u00a0\n\n### Root Cause Analysis\u00a0\n\nAn upstream infrastructure outage disrupted connectivity between PlayFab services and backend storage, causing request timeouts and elevated error rates across multiple APIs. The issue was external to PlayFab and self-resolved once the underlying infrastructure was restored.\u00a0\n\n### Action Items\u00a0\n\nAs part of our ongoing reliability investment, we are conducting a comprehensive assessment of our disaster recovery posture to improve resilience against upstream infrastructure disruptions. This includes evaluating regional redundancy for all critical data stores and developing documented recovery procedures to reduce the duration and impact of future incidents of this nature.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "minor",
145
- "last_seen": "2026-09-04T12:24:18Z",
146
  "resolved_at": "2026-05-29T16:34:19.985-07:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-05-28T22:24:29.667-07:00",
@@ -155,7 +155,7 @@
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "none",
158
- "last_seen": "2026-09-04T12:24:18Z",
159
  "resolved_at": "2026-05-19T20:16:47.354-07:00",
160
  "resolved_inferred": false,
161
  "started_at": "2026-05-19T18:05:20.673-07:00",
@@ -168,7 +168,7 @@
168
  "body": "This incident is now resolved. All players should have up-to-date transaction history.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "minor",
171
- "last_seen": "2026-09-04T12:24:18Z",
172
  "resolved_at": "2026-06-11T11:33:10.787-07:00",
173
  "resolved_inferred": false,
174
  "started_at": "2026-05-14T09:13:38.466-07:00",
@@ -181,7 +181,7 @@
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "none",
184
- "last_seen": "2026-09-04T12:24:18Z",
185
  "resolved_at": "2026-05-06T12:47:34.786-07:00",
186
  "resolved_inferred": false,
187
  "started_at": "2026-05-05T12:22:27.183-07:00",
@@ -194,7 +194,7 @@
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "major",
197
- "last_seen": "2026-09-04T12:24:18Z",
198
  "resolved_at": "2026-04-30T13:15:09.000-07:00",
199
  "resolved_inferred": false,
200
  "started_at": "2026-04-29T10:00:42.000-07:00",
@@ -207,7 +207,7 @@
207
  "body": "We observed an increase in error rates for Groups APIs between ~2 pm pacific through ~7 pm pacific on Tuesday April 7 (aka 21:00 UTC April 7 - 02:00 UTC April 8). \n\nThe initial root cause of this incident was a configuration change.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "none",
210
- "last_seen": "2026-09-04T12:24:18Z",
211
  "resolved_at": "2026-04-07T14:00:00.000-07:00",
212
  "resolved_inferred": false,
213
  "started_at": "2026-04-07T14:00:00.000-07:00",
@@ -220,7 +220,7 @@
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
- "last_seen": "2026-09-04T12:24:18Z",
224
  "resolved_at": "2026-03-24T15:30:31.319-07:00",
225
  "resolved_inferred": false,
226
  "started_at": "2026-03-24T13:05:12.519-07:00",
@@ -233,7 +233,7 @@
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
- "last_seen": "2026-09-04T12:24:18Z",
237
  "resolved_at": "2026-03-18T11:47:37.347-07:00",
238
  "resolved_inferred": false,
239
  "started_at": "2026-03-18T11:02:07.078-07:00",
@@ -246,7 +246,7 @@
246
  "body": "Some custom events sent through PlayFab WriteTelemetryEvents API were dropped between 03-03-2026 19:05 UTC to 03-05-2026 00:19 UTC. Our engineers have rolled out a fix, but unfortunately the custom events that were dropped during that window cannot be recovered.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "none",
249
- "last_seen": "2026-09-04T12:24:18Z",
250
  "resolved_at": "2026-03-04T16:00:00.000-08:00",
251
  "resolved_inferred": false,
252
  "started_at": "2026-03-03T11:00:00.000-08:00",
@@ -259,7 +259,7 @@
259
  "body": "On February 17, 2026, between approximately 10:00 AM and 11:14 AM Pacific Time, some customers experienced increased failures when calling the Client/LoginWith\\[Platform\\] APIs. The issue was caused by a code regression that inadvertently removed a required validation check, leading to internal server errors. We mitigated the issue by rolling back the update.\n\n### Impact\n\nDuring the impact window, customers experienced failed login attempts through the Client/LoginWith\\[Platform\\] APIs, with availability dropping to as low as 93%.\n\n### Root Cause Analysis\n\nA recent code change removed a necessary null check, which caused certain requests for these APIs to fail.\n\n### Action Items\n\nRolled back the service update to immediately restore API availability.\n\nDeployed a hotfix to correct the code regression. Tests were also added to prevent this issue from recurring.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "minor",
262
- "last_seen": "2026-09-04T12:24:18Z",
263
  "resolved_at": "2026-02-17T09:00:00.000-08:00",
264
  "resolved_inferred": false,
265
  "started_at": "2026-02-17T09:00:00.000-08:00",
@@ -272,7 +272,7 @@
272
  "body": "This incident has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "none",
275
- "last_seen": "2026-09-04T12:24:18Z",
276
  "resolved_at": "2026-02-13T11:47:25.422-08:00",
277
  "resolved_inferred": false,
278
  "started_at": "2026-02-12T12:11:33.049-08:00",
@@ -285,7 +285,7 @@
285
  "body": "This incident has been resolved.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "none",
288
- "last_seen": "2026-09-04T12:24:18Z",
289
  "resolved_at": "2026-02-09T13:27:03.922-08:00",
290
  "resolved_inferred": false,
291
  "started_at": "2026-02-09T13:26:43.033-08:00",
@@ -298,7 +298,7 @@
298
  "body": "Delays have been resolved. Data is up-to-date.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "minor",
301
- "last_seen": "2026-09-04T12:24:18Z",
302
  "resolved_at": "2026-02-06T15:45:00.000-08:00",
303
  "resolved_inferred": false,
304
  "started_at": "2026-02-06T15:22:09.000-08:00",
@@ -311,7 +311,7 @@
311
  "body": "InvalidRequest errors have subsided.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "major",
314
- "last_seen": "2026-09-04T12:24:18Z",
315
  "resolved_at": "2026-02-05T14:24:48.318-08:00",
316
  "resolved_inferred": false,
317
  "started_at": "2026-02-05T12:53:33.678-08:00",
@@ -324,7 +324,7 @@
324
  "body": "This incident has been resolved.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "minor",
327
- "last_seen": "2026-09-04T12:24:18Z",
328
  "resolved_at": "2026-02-03T02:00:09.000-08:00",
329
  "resolved_inferred": false,
330
  "started_at": "2026-02-02T10:30:33.000-08:00",
@@ -337,7 +337,7 @@
337
  "body": "On January 28, 2026, between approximately 1:35 PM and 8:10 PM PDT, some customers experienced delays related to ban processing. During this time, our global indexing pipeline for ban-related data fell behind after encountering invalid customer data that caused batch processing failures. We mitigated the issue by deploying a hotfix to skip invalid affected records, allowing the indexing pipeline to catch up and normal processing to resume.\n\n### Impact\n\nDuring the incident window \\(about 6 hours and 34 minutes\\), ban-related indexing was delayed. As a result, scenarios that rely on timely ban updates may have taken longer than expected to take effect. We did not observe data loss; the primary impact was delayed processing. Any bans enacted during the impact period were eventually applied.\n\n### Root Cause Analysis\n\nA customer-created record contained an invalid value that was interpreted incorrectly during decoding \\(in this case, an invalid date string\\). Because our validation did not sufficiently enforce expected formats for certain fields, the bad data made it into the ban-related data set and caused repeated batch failures in the indexing pipeline. Those failures prevented the pipeline from making forward progress until the problematic records were bypassed.\n\n### Action Items\n\nTo reduce the likelihood and impact of similar issues, we completed the following actions:\n\n* Deployed a hotfix to safely skip invalid records so indexing can continue even when encountering bad data.\n* Improved error logging in the indexing processor to speed up diagnosis if similar processing failures occur.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "major",
340
- "last_seen": "2026-09-04T12:24:18Z",
341
  "resolved_at": "2026-01-28T20:06:13.252-08:00",
342
  "resolved_inferred": false,
343
  "started_at": "2026-01-28T14:35:18.286-08:00",
@@ -350,7 +350,7 @@
350
  "body": "On January 18, 2026, between approximately 6:00 PM and 10:45 PM PT, some customers experienced delayed updates in the PlayFab Billing Summary report. The issue was triggered by a change in an external data query dependency, and service was restored after a hotfix was deployed and the processing pipelines were re-run.\n\n### Impact\n\nThe daily Billing Summary update \\(including the \u201clast updated\u201d timestamp, daily CSV, and refreshed month-to-date estimates\\) was delayed by roughly 4.5 hours. Customers viewing Billing Summary during that window may have seen estimates that were older than expected.\n\n### Root Cause Analysis\n\nAn external partner change introduced a new required parameter for a data update operation used by our billing reporting pipeline. This caused part of the daily aggregation and update flow to fail until we adjusted the operation and reprocessed the affected data.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we are taking the following actions:\n\n* Improving our monitoring process to more quickly detect failures in the end-to-end billing update flow so delays can be identified and addressed sooner.\n* Investigating improvements to communication with external dependency team for upcoming changes on their end",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "minor",
353
- "last_seen": "2026-09-04T12:24:18Z",
354
  "resolved_at": "2026-01-19T01:45:39.000-08:00",
355
  "resolved_inferred": false,
356
  "started_at": "2026-01-18T18:15:57.718-08:00",
@@ -363,7 +363,7 @@
363
  "body": "This incident has been resolved.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "major",
366
- "last_seen": "2026-09-04T12:24:18Z",
367
  "resolved_at": "2026-01-20T13:14:02.550-08:00",
368
  "resolved_inferred": false,
369
  "started_at": "2026-01-13T15:55:57.322-08:00",
@@ -376,7 +376,7 @@
376
  "body": "On January 13, 2026, between approximately 11:15 AM and 7:23 PM PST, some customers experienced increased failures when using PlayFab Matchmaking, including errors when calling matchmaking-related APIs \\(such as GetMatch\\). This was caused by a configuration update that applied more restrictive request limits than intended for some titles. We resolved the issue by rolling back the configuration change and monitoring service health to confirm recovery.\n\n### Impact\n\nA subset of titles using the PlayFab Matchmaking Service experienced elevated API failures, which could cause matchmaking flows to fail and lead to a degraded gameplay experience until the rollback was completed.\n\n### Root Cause Analysis\n\nA configuration change intended to adjust request limits did not map as expected to existing limits for certain APIs. As a result, some titles were throttled more aggressively than intended, increasing request failures. Because monitoring did not immediately highlight the affected titles, the issue was detected later and then mitigated by reverting the change.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following action:\n\n* Improved our throttling telemetry so request-throttling metrics are easier to interpret during investigations.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "minor",
379
- "last_seen": "2026-09-04T12:24:18Z",
380
  "resolved_at": "2026-01-13T19:18:59.575-08:00",
381
  "resolved_inferred": false,
382
  "started_at": "2026-01-13T11:15:54.000-08:00",
@@ -389,7 +389,7 @@
389
  "body": "Between December 5, 2025, 11:37 PST and December 22, 2025, 14:20 PST, some PlayFab customers experienced inaccurate metrics reporting for certain dashboards \\(which were underreported by as much as 30%\\). The issue was caused by an infrastructure misconfiguration.\n\n### Impact\n\nSome PlayFab dashboards displayed inaccurate or incomplete data during this period. Metrics such as API call volumes, login counts, and cloudscript processing times were underreported by up to 30%. No customer gameplay or operational functionality was affected, but visibility into service activity and performance was temporarily reduced.\n\n### Root Cause Analysis\n\nA component responsible for metrics reporting was misconfigured, leading to the data not being displayed in dashboards at full accuracy.\n\n### Action Items\n\n* We updated our infrastructure to ensure metrics are always sent to the correct environment.\n\n* We improved monitoring to better detect and alert on unexpected drops in metrics volume.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "major",
392
- "last_seen": "2026-09-04T12:24:18Z",
393
  "resolved_at": "2025-12-23T11:41:52.296-08:00",
394
  "resolved_inferred": false,
395
  "started_at": "2025-12-23T11:41:52.253-08:00",
@@ -402,7 +402,7 @@
402
  "body": "**Incident Overview**\u00a0\n\nBetween October 21st, 2025, and December 3rd, 2025, users were unable to redeem a subset of marketplace purchases for catalog items created during this window. The incident was caused by a misconfiguration affecting a redemption processor that prevented a subset of newly created items from being available for redemption. The issue was resolved by fixing the misconfiguration.\u00a0 \u00a0\n\n**Impact**\u00a0\n\nUsers\u00a0were unable to redeem a subset\u00a0\\(3-4%\\) of items that were created during the window. All purchases made during this period have been redeemable since the fix on December 3rd.\u00a0\n\n**Action Items**\u00a0\n\nTo prevent similar incidents from happening again, we have taken the following actions:\u00a0\n\n* Additional validation to avoid misconfigurations affecting the redemption processing system\u00a0\n\n* Enhanced alerting for the\u00a0redemption processor to improve detection of similar issues",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "minor",
405
- "last_seen": "2026-09-04T12:24:18Z",
406
  "resolved_at": "2025-12-04T09:51:33.931-08:00",
407
  "resolved_inferred": false,
408
  "started_at": "2025-12-03T14:02:17.727-08:00",
@@ -415,7 +415,7 @@
415
  "body": "On November 25, 2025, between 15:15 PST and 17:00 PST, some customers experienced reduced availability when accessing Leaderboard, Lobby and Game Saves APIs. The incident was caused by a DNS outage in the West US 3 region, which affected communication with our infrastructure. The issue was resolved automatically once the DNS service was restored.\n\n### Impact\n\nDuring the incident, the availability of the FindLobby and FindFriendLobbies APIs dropped to approximately 96%, the availability of all GameSave APIs dropped to an average of 80%, and downstream processing for Leaderboards was delayed. As a result, customers were unable to query for lobbies or upload new game saves using these APIs for about 1 hour and 45 minutes. Leaderboard updates were delayed. Service quality was temporarily below our standard threshold.\n\n### Root Cause Analysis\n\nThe incident was caused by a DNS outage in the West US 3 region. This outage disrupted communication between our Lobby, GameSave and Leaderboard services and their supporting infrastructure, resulting in reduced API availability. The root cause was related to an external dependency and not due to a code or configuration change within PlayFab.\n\n### Action Items\n\nTo prevent similar incidents in the future, we have enhanced our monitoring systems to detect and report anomalies in API availability more quickly. We are also reviewing our infrastructure dependencies to improve resiliency against external outages.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "minor",
418
- "last_seen": "2026-09-04T12:24:18Z",
419
  "resolved_at": "2025-11-25T17:18:58.595-08:00",
420
  "resolved_inferred": false,
421
  "started_at": "2025-11-25T16:53:21.841-08:00",
@@ -428,7 +428,7 @@
428
  "body": "On November 23rd\u201324th, 2025, some customers experienced errors when using PlayFab\u2019s Plan Recommendation and Pricing Sync features. The incident was caused by an authentication issue in a billing service component, which disrupted several related services. We resolved the issue by updating the connection logic for our data service.\n\n### Impact\n\nCustomers were unable to access plan recommendations and update workflows. The issue was detected by our monitoring systems and reported by customers.\n\n### Root Cause Analysis\n\nThe authentication errors were triggered by changes in the underlying .Net version, which affected how a billing service component connected to our data service.\n\n### Resolution\n\nWe updated the connection logic for the billing service component, restoring normal operation and notifying affected customers.\n\n### Action Items\n\n* Improved the connection logic for our data service in the affected billing service component.\n\n* Enhanced monitoring to detect authentication issues earlier.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "major",
431
- "last_seen": "2026-09-04T12:24:18Z",
432
  "resolved_at": "2025-11-24T15:25:28.371-08:00",
433
  "resolved_inferred": false,
434
  "started_at": "2025-11-24T11:37:02.906-08:00",
@@ -441,7 +441,7 @@
441
  "body": "On November 14, 2025, between 8:00 AM and 4:54 PM PST, some PlayFab customers experienced delays in Bulk Segmentation features. This resulted in delays in player profile updates, segment exports, and scheduled tasks. The issue was caused by a state in the ADX cluster powering the features, which led to the materialized view becoming unhealthy. We applied manual recovery steps and collaborated with the ADX team to resolve the problem, as the cluster was in a degraded state.\n\n### Impact\n\nCustomers experienced delays in player profile updates, segment exports, and scheduled tasks due to the degraded health of the player profile materialized view. Bulk Segmentation features were specifically impacted during this period.\n\n### Root Cause Analysis\n\nThe issue was triggered by an unexpected state in the ADX cluster powering the features, which caused materialized views to stop processing new data. This led to delays for customers and required manual recovery steps to restore normal functionality.\n\n### Action Items\n\n\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Implemented safeguards to prevent materialized views from entering an unhealthy state in the future.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "minor",
444
- "last_seen": "2026-09-04T12:24:18Z",
445
  "resolved_at": "2025-11-14T16:13:25.275-08:00",
446
  "resolved_inferred": false,
447
  "started_at": "2025-11-14T12:46:34.614-08:00",
@@ -454,7 +454,7 @@
454
  "body": "This incident has been resolved.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "critical",
457
- "last_seen": "2026-09-04T12:24:18Z",
458
  "resolved_at": "2025-10-29T16:00:23.000-07:00",
459
  "resolved_inferred": false,
460
  "started_at": "2025-10-29T09:17:52.065-07:00",
@@ -467,7 +467,7 @@
467
  "body": "This incident has been resolved.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "major",
470
- "last_seen": "2026-09-04T12:24:18Z",
471
  "resolved_at": "2025-10-24T06:55:13.561-07:00",
472
  "resolved_inferred": false,
473
  "started_at": "2025-10-23T21:32:28.476-07:00",
@@ -480,7 +480,7 @@
480
  "body": "This incident has been resolved.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "minor",
483
- "last_seen": "2026-09-04T12:24:18Z",
484
  "resolved_at": "2025-10-15T15:45:30.000-07:00",
485
  "resolved_inferred": false,
486
  "started_at": "2025-10-15T15:30:12.339-07:00",
@@ -493,7 +493,7 @@
493
  "body": "We are investigated an failure rate for the Client/LoginWithXbox API.",
494
  "first_seen": "2026-09-04T07:06:16Z",
495
  "impact": "none",
496
- "last_seen": "2026-09-04T12:24:18Z",
497
  "resolved_at": "2025-10-15T15:00:00.000-07:00",
498
  "resolved_inferred": false,
499
  "started_at": "2025-10-15T15:00:00.000-07:00",
@@ -506,7 +506,7 @@
506
  "body": "On October 9th, 2025, between 12:20 PM and 2:40 PM PDT, some customers experienced increased failures when accessing the GameClient/ConsumePS5Entitlements and GameClient/ConsumePSNEntitlements APIs, as well as a few related APIs. The incident was caused by an outage in a third-party dependency, which resulted in our APIs receiving increased exceptions and errors. The issue was resolved once the external outage ended and normal service resumed.\n\n### Impact\n\nCustomers were unable to successfully complete requests through affected entitlements APIs for approximately two hours. This resulted in failed attempts to consume entitlements, impacting the user experience for games relying on these APIs.\n\n### Root Cause Analysis\n\nThe root cause of the incident was an external issue: a service outage in a third-party dependency. As our APIs depend on calls to the external service for authentication and entitlement verification, the outage led to increased exceptions and errors being returned to our services.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n* Enhanced our monitoring and alerting systems to provide earlier detection of external partner outages affecting entitlements APIs.\n\n* Reviewed and improved our exception handling and error messaging to ensure clear communication to customers when third-party outages impact API availability.",
507
  "first_seen": "2026-09-04T07:06:16Z",
508
  "impact": "major",
509
- "last_seen": "2026-09-04T12:24:18Z",
510
  "resolved_at": "2025-10-09T14:40:12.926-07:00",
511
  "resolved_inferred": false,
512
  "started_at": "2025-10-09T12:54:59.999-07:00",
@@ -519,7 +519,7 @@
519
  "body": "On September 16, 2025, between 8:20 PM and 10:42 PM PDT, some customers experienced issues with PlayFab Lobbies. During this period, players across all titles using Lobbies were unable to create, join, or update lobbies, although search APIs remained functional. The incident was caused by a maintenance event internal to our Redis infrastructure, which disrupted connectivity between the Lobby service and Redis. We resolved the issue by rebooting the Redis instances, restoring connectivity and service functionality.\n\n### Impact\n\nPlayers were unable to create, join, or update lobbies across all titles that use the PlayFab Lobby system for approximately 2 hours and 22 minutes. While search APIs continued to work, players could not join lobbies they found during this time.\n\n### Root Cause Analysis\n\nThe root cause of the incident was a maintenance event within our Redis infrastructure that unexpectedly killed connectivity for the Lobby service. While we have the capability to schedule maintenance, this event occurred exactly when the impact started, leading to the service disruption.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n* Updated the Lobby service to better display its status on our service overview dashboard, which will enhance visibility and expedite future detection and mitigation efforts.\n\n* Improved our internal processes for scheduling and communicating maintenance events that could impact service connectivity.",
520
  "first_seen": "2026-09-04T07:06:16Z",
521
  "impact": "major",
522
- "last_seen": "2026-09-04T12:24:18Z",
523
  "resolved_at": "2025-09-16T22:35:42.967-07:00",
524
  "resolved_inferred": false,
525
  "started_at": "2025-09-16T21:01:00.561-07:00",
@@ -532,7 +532,7 @@
532
  "body": "On September 12, 2025, between 01:42 AM and 03:09 AM PDT, some PlayFab customers experienced issues authenticating with Photon APIs. The incident was caused by unexpected traffic patterns to Photon API endpoints, which resulted in a hot partition and degraded availability. We resolved the issue by setting a throttle limit for the affected API endpoint.\n\n### Impact\n\nDuring the incident, customers with Photon tokens stored on the hot partition may have been unable to authenticate. The availability for Photon APIs dropped to as low as 78.8%, impacting service reliability for approximately 1 hour and 27 minutes.\n\n### Root Cause Analysis\n\nThe root cause was an unexpected traffic pattern on the Photon authentication API endpoint. A large call volume on this endpoint put strain on database lookup tables for logging in the user. The call volume was outside normal parameters.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Cached results from previous Photon sessions to reduce strain on the database infrastructure.\n\n\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Adjusted the title rate limit for the Photon APIs.",
533
  "first_seen": "2026-09-04T07:06:16Z",
534
  "impact": "minor",
535
- "last_seen": "2026-09-04T12:24:18Z",
536
  "resolved_at": "2025-09-12T03:19:40.781-07:00",
537
  "resolved_inferred": false,
538
  "started_at": "2025-09-12T02:39:40.492-07:00",
@@ -545,7 +545,7 @@
545
  "body": "This incident has been resolved. All impacted scorecards are regenerated.",
546
  "first_seen": "2026-09-04T07:06:16Z",
547
  "impact": "minor",
548
- "last_seen": "2026-09-04T12:24:18Z",
549
  "resolved_at": "2025-09-10T09:24:19.925-07:00",
550
  "resolved_inferred": false,
551
  "started_at": "2025-09-09T16:28:19.923-07:00",
@@ -558,7 +558,7 @@
558
  "body": "This incident has been resolved. Impact was observed from 20:40 PDT to 21:30 PDT. Note that this was after the previous related incident.",
559
  "first_seen": "2026-09-04T07:06:16Z",
560
  "impact": "major",
561
- "last_seen": "2026-09-04T12:24:18Z",
562
  "resolved_at": "2025-09-01T11:09:03.144-07:00",
563
  "resolved_inferred": false,
564
  "started_at": "2025-08-31T20:40:49.000-07:00",
@@ -571,7 +571,7 @@
571
  "body": "On August 31, 2025, between 11:50 AM and 7:53 PM PDT, some customers experienced a complete outage of PlayFab Matchmaking. The incident was caused by a regression in the authentication library, which led to unexpected high call rates to Entra ID for token acquisition, resulting in service throttling and failures. We resolved the issue by increasing authentication rate limits, updating the authentication code, recycling affected application instances, and isolating impacted titles into dedicated deployments.\n\n### Impact\n\nDuring the outage, matchmaking services were unavailable for all affected titles, preventing players from joining matches. Notification failures also occurred, resulting in players being stuck in matchmaking and not receiving proper updates.\n\n### Root Cause Analysis\n\nThe root cause of the incident was a regression in the updated authentication library, which failed to cache tokens as expected. This led to a surge in token requests to Entra ID, causing throttling and authentication failures across the service. The updated library created new instances for each authentication attempt, breaking the caching mechanism and increasing network traffic unexpectedly.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n* Implemented service-level caching for authentication tokens to reduce unnecessary external calls.\n* Enhanced monitoring and diagnostics to detect abnormal network patterns and authentication failures more quickly.\n* Improved notification handling and recycling processes to prevent players from being stuck in matchmaking.",
572
  "first_seen": "2026-09-04T07:06:16Z",
573
  "impact": "major",
574
- "last_seen": "2026-09-04T12:24:18Z",
575
  "resolved_at": "2025-08-31T20:28:48.383-07:00",
576
  "resolved_inferred": false,
577
  "started_at": "2025-08-31T12:00:46.000-07:00",
@@ -584,7 +584,7 @@
584
  "body": "On August 19, 2025, between 9:32 AM and 10:50 AM PDT, some customers experienced failures when calling PlayFab APIs due to issues with entity token validation. The incident was caused by a switch in the JSON library used for serialization and deserialization of entity tokens \\(for improved security and efficiency\\). We resolved the issue by rolling back the serialization change and advising impacted customers to refresh their tokens.\n\n### Impact\n\nDuring the incident, calls to validate entity tokens failed, preventing all further API calls using those tokens. Affected APIs primarily included WriteTelemetryEvents, Catalog search, GetPlayFabIdFrom\\*Id, ExecuteCloudScript, and Group-related APIs. This resulted in service disruption for customers relying on these endpoints.\n\n### Root Cause Analysis\n\nThe root cause was a deployment that switched the JSON library responsible for entity token serialization. After rolling back the change, errors persisted for tokens minted during the incident window, requiring customers to refresh their tokens.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n* Added documentation to the entity token release process to highlight serialization risks and warnings.\n\n* Implemented additional backcompat token tests for the entity token to expand test",
585
  "first_seen": "2026-09-04T07:06:16Z",
586
  "impact": "major",
587
- "last_seen": "2026-09-04T12:24:18Z",
588
  "resolved_at": "2025-08-19T13:44:55.608-07:00",
589
  "resolved_inferred": false,
590
  "started_at": "2025-08-19T09:30:18.000-07:00",
@@ -597,7 +597,7 @@
597
  "body": "This incident has been resolved.",
598
  "first_seen": "2026-09-04T07:06:16Z",
599
  "impact": "none",
600
- "last_seen": "2026-09-04T12:24:18Z",
601
  "resolved_at": "2025-08-14T15:11:19.249-07:00",
602
  "resolved_inferred": false,
603
  "started_at": "2025-08-14T14:15:26.000-07:00",
@@ -610,7 +610,7 @@
610
  "body": "On August 8, 2025, between 10:55 PM and 1:15 AM PDT, some customers experienced errors and delays when searching or purchasing catalog items through PlayFab\u2019s APIs. The incident was caused by a faulty service configuration intended for experimentation in a single region, which was mistakenly deployed to all regions due to human error. This misconfiguration led to increased internal server errors and service unavailability. The issue was resolved by rolling back the faulty configuration and confirming service recovery through monitoring and health checks.\n\n### Impact\n\nApproximately 12,000 players were affected, unable to search or purchase catalog items. During the outage, the latency of Catalog APIs \\(particularly SearchItems and GetItems\\) increased significantly, and many requests were rejected with a \u201cService unavailable\u201d status.\n\n### Root Cause Analysis\n\nThe root cause was a human error in deploying a service configuration intended for limited traffic in a single region. Instead, the configuration update was applied to all regions, increasing resource pressure and causing a spike in internal server errors for Catalog APIs dependent on storage. This led to widespread request failures and degraded service availability.\n\n### Action Items\n\n* Rolled back the faulty service configuration to restore normal operation.\n* Improved deployment validation procedures to ensure experimental changes are restricted to intended regions.\n* Enhanced monitoring and alerting systems to detect and report anomalies in API error rates and service health more rapidly.",
611
  "first_seen": "2026-09-04T07:06:16Z",
612
  "impact": "none",
613
- "last_seen": "2026-09-04T12:24:18Z",
614
  "resolved_at": "2025-08-08T21:00:00.000-07:00",
615
  "resolved_inferred": false,
616
  "started_at": "2025-08-08T21:00:00.000-07:00",
@@ -623,7 +623,7 @@
623
  "body": "On July 31, 2025, between 10:30 AM and 7:29 PM PDT, some customers experienced significant delays when using PlayStream actions for rules and segments. Action executions were delayed, with a maximum delay of over 500 minutes at peak. The incident was caused by a combination of load and configuration values for the maximum number of records each processor could read at once, which, combined with pod health logic, led to excessive memory usage and processor failures. We resolved the issue by reducing the configuration value, which restored healthy processing across all partitions.\n\n### Impact\n\nAll PlayFab titles using PlayStream actions for rules and segments were impacted. Action executions were delayed but not dropped; however, the prolonged delay meant that some actions may not have been useful by the time they were processed.\n\n### Root Cause Analysis\n\nThe incident was caused by a misconfiguration in the number of records each processor attempted to read, combined with a change in the logic for partition allocation per processor. As processor pods failed due to memory exhaustion, the remaining healthy pods became overloaded, leading to a cascading failure and increasing delays in action processing.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n* We reduced the maximum number of records each processor can read at once, improving processor reliability and preventing memory exhaustion.\n* We improved our monitoring and alerting to detect abnormal processor delays and memory usage earlier.",
624
  "first_seen": "2026-09-04T07:06:16Z",
625
  "impact": "minor",
626
- "last_seen": "2026-09-04T12:24:18Z",
627
  "resolved_at": "2025-07-31T21:55:03.196-07:00",
628
  "resolved_inferred": false,
629
  "started_at": "2025-07-31T15:17:00.765-07:00",
 
3
  "slug": "playfab",
4
  "platform": "statuspage",
5
  "status_url": "https://status.playfab.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "This incident has been resolved.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "major",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-08-27T18:34:07.423-07:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-08-27T11:12:17.933-07:00",
 
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "none",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2026-08-23T15:34:54.831-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2026-08-23T08:42:44.852-07:00",
 
38
  "body": "This incident has been resolved.",
39
  "first_seen": "2026-09-04T07:06:16Z",
40
  "impact": "major",
41
+ "last_seen": "2026-09-04T14:19:03Z",
42
  "resolved_at": "2026-08-07T21:09:06.038-07:00",
43
  "resolved_inferred": false,
44
  "started_at": "2026-08-07T10:47:54.381-07:00",
 
51
  "body": "This incident has been resolved.",
52
  "first_seen": "2026-09-04T07:06:16Z",
53
  "impact": "major",
54
+ "last_seen": "2026-09-04T14:19:03Z",
55
  "resolved_at": "2026-07-23T12:01:47.891-07:00",
56
  "resolved_inferred": false,
57
  "started_at": "2026-07-23T09:11:33.782-07:00",
 
64
  "body": "This incident has been resolved.",
65
  "first_seen": "2026-09-04T07:06:16Z",
66
  "impact": "major",
67
+ "last_seen": "2026-09-04T14:19:03Z",
68
  "resolved_at": "2026-07-21T08:24:00.219-07:00",
69
  "resolved_inferred": false,
70
  "started_at": "2026-07-16T14:37:44.991-07:00",
 
77
  "body": "The incident is now resolved",
78
  "first_seen": "2026-09-04T07:06:16Z",
79
  "impact": "none",
80
+ "last_seen": "2026-09-04T14:19:03Z",
81
  "resolved_at": "2026-07-02T13:05:51.346-07:00",
82
  "resolved_inferred": false,
83
  "started_at": "2026-07-02T12:32:14.608-07:00",
 
90
  "body": "This incident has been resolved.",
91
  "first_seen": "2026-09-04T07:06:16Z",
92
  "impact": "none",
93
+ "last_seen": "2026-09-04T14:19:03Z",
94
  "resolved_at": "2026-06-23T19:52:29.691-07:00",
95
  "resolved_inferred": false,
96
  "started_at": "2026-06-23T18:02:09.014-07:00",
 
103
  "body": "This incident has been resolved.",
104
  "first_seen": "2026-09-04T07:06:16Z",
105
  "impact": "minor",
106
+ "last_seen": "2026-09-04T14:19:03Z",
107
  "resolved_at": "2026-06-16T13:14:31.380-07:00",
108
  "resolved_inferred": false,
109
  "started_at": "2026-06-12T13:51:24.295-07:00",
 
116
  "body": "Some APIs temporarily received HTTP 429 errors.",
117
  "first_seen": "2026-09-04T07:06:16Z",
118
  "impact": "none",
119
+ "last_seen": "2026-09-04T14:19:03Z",
120
  "resolved_at": "2026-06-08T08:30:00.000-07:00",
121
  "resolved_inferred": false,
122
  "started_at": "2026-06-08T08:30:00.000-07:00",
 
129
  "body": "This incident has been resolved.",
130
  "first_seen": "2026-09-04T07:06:16Z",
131
  "impact": "minor",
132
+ "last_seen": "2026-09-04T14:19:03Z",
133
  "resolved_at": "2026-06-19T09:12:31.000-07:00",
134
  "resolved_inferred": false,
135
  "started_at": "2026-05-30T13:33:06.122-07:00",
 
142
  "body": "On May 29, 2026, between approximately 9:00 PM and 10:09 PM Pacific Time, some customers experienced increased failures and timeouts across multiple PlayFab APIs. The issue was caused by an upstream infrastructure outage in the hosting environment that disrupted connectivity to backend storage services. The issue auto-resolved once the upstream infrastructure problem was mitigated.\u00a0\n\n### Impact\u00a0\n\nDuring the impact window, customers experienced elevated error rates, timeouts, and connection disruptions when calling PlayFab APIs. Services including Lobby, Matchmaking, and real-time messaging were most heavily affected, with availability for those services degraded to between 75% and 95%. Multiple titles were impacted during the approximately 26-minute incident window.\u00a0\n\n### Root Cause Analysis\u00a0\n\nAn upstream infrastructure outage disrupted connectivity between PlayFab services and backend storage, causing request timeouts and elevated error rates across multiple APIs. The issue was external to PlayFab and self-resolved once the underlying infrastructure was restored.\u00a0\n\n### Action Items\u00a0\n\nAs part of our ongoing reliability investment, we are conducting a comprehensive assessment of our disaster recovery posture to improve resilience against upstream infrastructure disruptions. This includes evaluating regional redundancy for all critical data stores and developing documented recovery procedures to reduce the duration and impact of future incidents of this nature.",
143
  "first_seen": "2026-09-04T07:06:16Z",
144
  "impact": "minor",
145
+ "last_seen": "2026-09-04T14:19:03Z",
146
  "resolved_at": "2026-05-29T16:34:19.985-07:00",
147
  "resolved_inferred": false,
148
  "started_at": "2026-05-28T22:24:29.667-07:00",
 
155
  "body": "This incident has been resolved.",
156
  "first_seen": "2026-09-04T07:06:16Z",
157
  "impact": "none",
158
+ "last_seen": "2026-09-04T14:19:03Z",
159
  "resolved_at": "2026-05-19T20:16:47.354-07:00",
160
  "resolved_inferred": false,
161
  "started_at": "2026-05-19T18:05:20.673-07:00",
 
168
  "body": "This incident is now resolved. All players should have up-to-date transaction history.",
169
  "first_seen": "2026-09-04T07:06:16Z",
170
  "impact": "minor",
171
+ "last_seen": "2026-09-04T14:19:03Z",
172
  "resolved_at": "2026-06-11T11:33:10.787-07:00",
173
  "resolved_inferred": false,
174
  "started_at": "2026-05-14T09:13:38.466-07:00",
 
181
  "body": "This incident has been resolved.",
182
  "first_seen": "2026-09-04T07:06:16Z",
183
  "impact": "none",
184
+ "last_seen": "2026-09-04T14:19:03Z",
185
  "resolved_at": "2026-05-06T12:47:34.786-07:00",
186
  "resolved_inferred": false,
187
  "started_at": "2026-05-05T12:22:27.183-07:00",
 
194
  "body": "This incident has been resolved.",
195
  "first_seen": "2026-09-04T07:06:16Z",
196
  "impact": "major",
197
+ "last_seen": "2026-09-04T14:19:03Z",
198
  "resolved_at": "2026-04-30T13:15:09.000-07:00",
199
  "resolved_inferred": false,
200
  "started_at": "2026-04-29T10:00:42.000-07:00",
 
207
  "body": "We observed an increase in error rates for Groups APIs between ~2 pm pacific through ~7 pm pacific on Tuesday April 7 (aka 21:00 UTC April 7 - 02:00 UTC April 8). \n\nThe initial root cause of this incident was a configuration change.",
208
  "first_seen": "2026-09-04T07:06:16Z",
209
  "impact": "none",
210
+ "last_seen": "2026-09-04T14:19:03Z",
211
  "resolved_at": "2026-04-07T14:00:00.000-07:00",
212
  "resolved_inferred": false,
213
  "started_at": "2026-04-07T14:00:00.000-07:00",
 
220
  "body": "This incident has been resolved.",
221
  "first_seen": "2026-09-04T07:06:16Z",
222
  "impact": "minor",
223
+ "last_seen": "2026-09-04T14:19:03Z",
224
  "resolved_at": "2026-03-24T15:30:31.319-07:00",
225
  "resolved_inferred": false,
226
  "started_at": "2026-03-24T13:05:12.519-07:00",
 
233
  "body": "This incident has been resolved.",
234
  "first_seen": "2026-09-04T07:06:16Z",
235
  "impact": "major",
236
+ "last_seen": "2026-09-04T14:19:03Z",
237
  "resolved_at": "2026-03-18T11:47:37.347-07:00",
238
  "resolved_inferred": false,
239
  "started_at": "2026-03-18T11:02:07.078-07:00",
 
246
  "body": "Some custom events sent through PlayFab WriteTelemetryEvents API were dropped between 03-03-2026 19:05 UTC to 03-05-2026 00:19 UTC. Our engineers have rolled out a fix, but unfortunately the custom events that were dropped during that window cannot be recovered.",
247
  "first_seen": "2026-09-04T07:06:16Z",
248
  "impact": "none",
249
+ "last_seen": "2026-09-04T14:19:03Z",
250
  "resolved_at": "2026-03-04T16:00:00.000-08:00",
251
  "resolved_inferred": false,
252
  "started_at": "2026-03-03T11:00:00.000-08:00",
 
259
  "body": "On February 17, 2026, between approximately 10:00 AM and 11:14 AM Pacific Time, some customers experienced increased failures when calling the Client/LoginWith\\[Platform\\] APIs. The issue was caused by a code regression that inadvertently removed a required validation check, leading to internal server errors. We mitigated the issue by rolling back the update.\n\n### Impact\n\nDuring the impact window, customers experienced failed login attempts through the Client/LoginWith\\[Platform\\] APIs, with availability dropping to as low as 93%.\n\n### Root Cause Analysis\n\nA recent code change removed a necessary null check, which caused certain requests for these APIs to fail.\n\n### Action Items\n\nRolled back the service update to immediately restore API availability.\n\nDeployed a hotfix to correct the code regression. Tests were also added to prevent this issue from recurring.",
260
  "first_seen": "2026-09-04T07:06:16Z",
261
  "impact": "minor",
262
+ "last_seen": "2026-09-04T14:19:03Z",
263
  "resolved_at": "2026-02-17T09:00:00.000-08:00",
264
  "resolved_inferred": false,
265
  "started_at": "2026-02-17T09:00:00.000-08:00",
 
272
  "body": "This incident has been resolved.",
273
  "first_seen": "2026-09-04T07:06:16Z",
274
  "impact": "none",
275
+ "last_seen": "2026-09-04T14:19:03Z",
276
  "resolved_at": "2026-02-13T11:47:25.422-08:00",
277
  "resolved_inferred": false,
278
  "started_at": "2026-02-12T12:11:33.049-08:00",
 
285
  "body": "This incident has been resolved.",
286
  "first_seen": "2026-09-04T07:06:16Z",
287
  "impact": "none",
288
+ "last_seen": "2026-09-04T14:19:03Z",
289
  "resolved_at": "2026-02-09T13:27:03.922-08:00",
290
  "resolved_inferred": false,
291
  "started_at": "2026-02-09T13:26:43.033-08:00",
 
298
  "body": "Delays have been resolved. Data is up-to-date.",
299
  "first_seen": "2026-09-04T07:06:16Z",
300
  "impact": "minor",
301
+ "last_seen": "2026-09-04T14:19:03Z",
302
  "resolved_at": "2026-02-06T15:45:00.000-08:00",
303
  "resolved_inferred": false,
304
  "started_at": "2026-02-06T15:22:09.000-08:00",
 
311
  "body": "InvalidRequest errors have subsided.",
312
  "first_seen": "2026-09-04T07:06:16Z",
313
  "impact": "major",
314
+ "last_seen": "2026-09-04T14:19:03Z",
315
  "resolved_at": "2026-02-05T14:24:48.318-08:00",
316
  "resolved_inferred": false,
317
  "started_at": "2026-02-05T12:53:33.678-08:00",
 
324
  "body": "This incident has been resolved.",
325
  "first_seen": "2026-09-04T07:06:16Z",
326
  "impact": "minor",
327
+ "last_seen": "2026-09-04T14:19:03Z",
328
  "resolved_at": "2026-02-03T02:00:09.000-08:00",
329
  "resolved_inferred": false,
330
  "started_at": "2026-02-02T10:30:33.000-08:00",
 
337
  "body": "On January 28, 2026, between approximately 1:35 PM and 8:10 PM PDT, some customers experienced delays related to ban processing. During this time, our global indexing pipeline for ban-related data fell behind after encountering invalid customer data that caused batch processing failures. We mitigated the issue by deploying a hotfix to skip invalid affected records, allowing the indexing pipeline to catch up and normal processing to resume.\n\n### Impact\n\nDuring the incident window \\(about 6 hours and 34 minutes\\), ban-related indexing was delayed. As a result, scenarios that rely on timely ban updates may have taken longer than expected to take effect. We did not observe data loss; the primary impact was delayed processing. Any bans enacted during the impact period were eventually applied.\n\n### Root Cause Analysis\n\nA customer-created record contained an invalid value that was interpreted incorrectly during decoding \\(in this case, an invalid date string\\). Because our validation did not sufficiently enforce expected formats for certain fields, the bad data made it into the ban-related data set and caused repeated batch failures in the indexing pipeline. Those failures prevented the pipeline from making forward progress until the problematic records were bypassed.\n\n### Action Items\n\nTo reduce the likelihood and impact of similar issues, we completed the following actions:\n\n* Deployed a hotfix to safely skip invalid records so indexing can continue even when encountering bad data.\n* Improved error logging in the indexing processor to speed up diagnosis if similar processing failures occur.",
338
  "first_seen": "2026-09-04T07:06:16Z",
339
  "impact": "major",
340
+ "last_seen": "2026-09-04T14:19:03Z",
341
  "resolved_at": "2026-01-28T20:06:13.252-08:00",
342
  "resolved_inferred": false,
343
  "started_at": "2026-01-28T14:35:18.286-08:00",
 
350
  "body": "On January 18, 2026, between approximately 6:00 PM and 10:45 PM PT, some customers experienced delayed updates in the PlayFab Billing Summary report. The issue was triggered by a change in an external data query dependency, and service was restored after a hotfix was deployed and the processing pipelines were re-run.\n\n### Impact\n\nThe daily Billing Summary update \\(including the \u201clast updated\u201d timestamp, daily CSV, and refreshed month-to-date estimates\\) was delayed by roughly 4.5 hours. Customers viewing Billing Summary during that window may have seen estimates that were older than expected.\n\n### Root Cause Analysis\n\nAn external partner change introduced a new required parameter for a data update operation used by our billing reporting pipeline. This caused part of the daily aggregation and update flow to fail until we adjusted the operation and reprocessed the affected data.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we are taking the following actions:\n\n* Improving our monitoring process to more quickly detect failures in the end-to-end billing update flow so delays can be identified and addressed sooner.\n* Investigating improvements to communication with external dependency team for upcoming changes on their end",
351
  "first_seen": "2026-09-04T07:06:16Z",
352
  "impact": "minor",
353
+ "last_seen": "2026-09-04T14:19:03Z",
354
  "resolved_at": "2026-01-19T01:45:39.000-08:00",
355
  "resolved_inferred": false,
356
  "started_at": "2026-01-18T18:15:57.718-08:00",
 
363
  "body": "This incident has been resolved.",
364
  "first_seen": "2026-09-04T07:06:16Z",
365
  "impact": "major",
366
+ "last_seen": "2026-09-04T14:19:03Z",
367
  "resolved_at": "2026-01-20T13:14:02.550-08:00",
368
  "resolved_inferred": false,
369
  "started_at": "2026-01-13T15:55:57.322-08:00",
 
376
  "body": "On January 13, 2026, between approximately 11:15 AM and 7:23 PM PST, some customers experienced increased failures when using PlayFab Matchmaking, including errors when calling matchmaking-related APIs \\(such as GetMatch\\). This was caused by a configuration update that applied more restrictive request limits than intended for some titles. We resolved the issue by rolling back the configuration change and monitoring service health to confirm recovery.\n\n### Impact\n\nA subset of titles using the PlayFab Matchmaking Service experienced elevated API failures, which could cause matchmaking flows to fail and lead to a degraded gameplay experience until the rollback was completed.\n\n### Root Cause Analysis\n\nA configuration change intended to adjust request limits did not map as expected to existing limits for certain APIs. As a result, some titles were throttled more aggressively than intended, increasing request failures. Because monitoring did not immediately highlight the affected titles, the issue was detected later and then mitigated by reverting the change.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following action:\n\n* Improved our throttling telemetry so request-throttling metrics are easier to interpret during investigations.",
377
  "first_seen": "2026-09-04T07:06:16Z",
378
  "impact": "minor",
379
+ "last_seen": "2026-09-04T14:19:03Z",
380
  "resolved_at": "2026-01-13T19:18:59.575-08:00",
381
  "resolved_inferred": false,
382
  "started_at": "2026-01-13T11:15:54.000-08:00",
 
389
  "body": "Between December 5, 2025, 11:37 PST and December 22, 2025, 14:20 PST, some PlayFab customers experienced inaccurate metrics reporting for certain dashboards \\(which were underreported by as much as 30%\\). The issue was caused by an infrastructure misconfiguration.\n\n### Impact\n\nSome PlayFab dashboards displayed inaccurate or incomplete data during this period. Metrics such as API call volumes, login counts, and cloudscript processing times were underreported by up to 30%. No customer gameplay or operational functionality was affected, but visibility into service activity and performance was temporarily reduced.\n\n### Root Cause Analysis\n\nA component responsible for metrics reporting was misconfigured, leading to the data not being displayed in dashboards at full accuracy.\n\n### Action Items\n\n* We updated our infrastructure to ensure metrics are always sent to the correct environment.\n\n* We improved monitoring to better detect and alert on unexpected drops in metrics volume.",
390
  "first_seen": "2026-09-04T07:06:16Z",
391
  "impact": "major",
392
+ "last_seen": "2026-09-04T14:19:03Z",
393
  "resolved_at": "2025-12-23T11:41:52.296-08:00",
394
  "resolved_inferred": false,
395
  "started_at": "2025-12-23T11:41:52.253-08:00",
 
402
  "body": "**Incident Overview**\u00a0\n\nBetween October 21st, 2025, and December 3rd, 2025, users were unable to redeem a subset of marketplace purchases for catalog items created during this window. The incident was caused by a misconfiguration affecting a redemption processor that prevented a subset of newly created items from being available for redemption. The issue was resolved by fixing the misconfiguration.\u00a0 \u00a0\n\n**Impact**\u00a0\n\nUsers\u00a0were unable to redeem a subset\u00a0\\(3-4%\\) of items that were created during the window. All purchases made during this period have been redeemable since the fix on December 3rd.\u00a0\n\n**Action Items**\u00a0\n\nTo prevent similar incidents from happening again, we have taken the following actions:\u00a0\n\n* Additional validation to avoid misconfigurations affecting the redemption processing system\u00a0\n\n* Enhanced alerting for the\u00a0redemption processor to improve detection of similar issues",
403
  "first_seen": "2026-09-04T07:06:16Z",
404
  "impact": "minor",
405
+ "last_seen": "2026-09-04T14:19:03Z",
406
  "resolved_at": "2025-12-04T09:51:33.931-08:00",
407
  "resolved_inferred": false,
408
  "started_at": "2025-12-03T14:02:17.727-08:00",
 
415
  "body": "On November 25, 2025, between 15:15 PST and 17:00 PST, some customers experienced reduced availability when accessing Leaderboard, Lobby and Game Saves APIs. The incident was caused by a DNS outage in the West US 3 region, which affected communication with our infrastructure. The issue was resolved automatically once the DNS service was restored.\n\n### Impact\n\nDuring the incident, the availability of the FindLobby and FindFriendLobbies APIs dropped to approximately 96%, the availability of all GameSave APIs dropped to an average of 80%, and downstream processing for Leaderboards was delayed. As a result, customers were unable to query for lobbies or upload new game saves using these APIs for about 1 hour and 45 minutes. Leaderboard updates were delayed. Service quality was temporarily below our standard threshold.\n\n### Root Cause Analysis\n\nThe incident was caused by a DNS outage in the West US 3 region. This outage disrupted communication between our Lobby, GameSave and Leaderboard services and their supporting infrastructure, resulting in reduced API availability. The root cause was related to an external dependency and not due to a code or configuration change within PlayFab.\n\n### Action Items\n\nTo prevent similar incidents in the future, we have enhanced our monitoring systems to detect and report anomalies in API availability more quickly. We are also reviewing our infrastructure dependencies to improve resiliency against external outages.",
416
  "first_seen": "2026-09-04T07:06:16Z",
417
  "impact": "minor",
418
+ "last_seen": "2026-09-04T14:19:03Z",
419
  "resolved_at": "2025-11-25T17:18:58.595-08:00",
420
  "resolved_inferred": false,
421
  "started_at": "2025-11-25T16:53:21.841-08:00",
 
428
  "body": "On November 23rd\u201324th, 2025, some customers experienced errors when using PlayFab\u2019s Plan Recommendation and Pricing Sync features. The incident was caused by an authentication issue in a billing service component, which disrupted several related services. We resolved the issue by updating the connection logic for our data service.\n\n### Impact\n\nCustomers were unable to access plan recommendations and update workflows. The issue was detected by our monitoring systems and reported by customers.\n\n### Root Cause Analysis\n\nThe authentication errors were triggered by changes in the underlying .Net version, which affected how a billing service component connected to our data service.\n\n### Resolution\n\nWe updated the connection logic for the billing service component, restoring normal operation and notifying affected customers.\n\n### Action Items\n\n* Improved the connection logic for our data service in the affected billing service component.\n\n* Enhanced monitoring to detect authentication issues earlier.",
429
  "first_seen": "2026-09-04T07:06:16Z",
430
  "impact": "major",
431
+ "last_seen": "2026-09-04T14:19:03Z",
432
  "resolved_at": "2025-11-24T15:25:28.371-08:00",
433
  "resolved_inferred": false,
434
  "started_at": "2025-11-24T11:37:02.906-08:00",
 
441
  "body": "On November 14, 2025, between 8:00 AM and 4:54 PM PST, some PlayFab customers experienced delays in Bulk Segmentation features. This resulted in delays in player profile updates, segment exports, and scheduled tasks. The issue was caused by a state in the ADX cluster powering the features, which led to the materialized view becoming unhealthy. We applied manual recovery steps and collaborated with the ADX team to resolve the problem, as the cluster was in a degraded state.\n\n### Impact\n\nCustomers experienced delays in player profile updates, segment exports, and scheduled tasks due to the degraded health of the player profile materialized view. Bulk Segmentation features were specifically impacted during this period.\n\n### Root Cause Analysis\n\nThe issue was triggered by an unexpected state in the ADX cluster powering the features, which caused materialized views to stop processing new data. This led to delays for customers and required manual recovery steps to restore normal functionality.\n\n### Action Items\n\n\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Implemented safeguards to prevent materialized views from entering an unhealthy state in the future.",
442
  "first_seen": "2026-09-04T07:06:16Z",
443
  "impact": "minor",
444
+ "last_seen": "2026-09-04T14:19:03Z",
445
  "resolved_at": "2025-11-14T16:13:25.275-08:00",
446
  "resolved_inferred": false,
447
  "started_at": "2025-11-14T12:46:34.614-08:00",
 
454
  "body": "This incident has been resolved.",
455
  "first_seen": "2026-09-04T07:06:16Z",
456
  "impact": "critical",
457
+ "last_seen": "2026-09-04T14:19:03Z",
458
  "resolved_at": "2025-10-29T16:00:23.000-07:00",
459
  "resolved_inferred": false,
460
  "started_at": "2025-10-29T09:17:52.065-07:00",
 
467
  "body": "This incident has been resolved.",
468
  "first_seen": "2026-09-04T07:06:16Z",
469
  "impact": "major",
470
+ "last_seen": "2026-09-04T14:19:03Z",
471
  "resolved_at": "2025-10-24T06:55:13.561-07:00",
472
  "resolved_inferred": false,
473
  "started_at": "2025-10-23T21:32:28.476-07:00",
 
480
  "body": "This incident has been resolved.",
481
  "first_seen": "2026-09-04T07:06:16Z",
482
  "impact": "minor",
483
+ "last_seen": "2026-09-04T14:19:03Z",
484
  "resolved_at": "2025-10-15T15:45:30.000-07:00",
485
  "resolved_inferred": false,
486
  "started_at": "2025-10-15T15:30:12.339-07:00",
 
493
  "body": "We are investigated an failure rate for the Client/LoginWithXbox API.",
494
  "first_seen": "2026-09-04T07:06:16Z",
495
  "impact": "none",
496
+ "last_seen": "2026-09-04T14:19:03Z",
497
  "resolved_at": "2025-10-15T15:00:00.000-07:00",
498
  "resolved_inferred": false,
499
  "started_at": "2025-10-15T15:00:00.000-07:00",
 
506
  "body": "On October 9th, 2025, between 12:20 PM and 2:40 PM PDT, some customers experienced increased failures when accessing the GameClient/ConsumePS5Entitlements and GameClient/ConsumePSNEntitlements APIs, as well as a few related APIs. The incident was caused by an outage in a third-party dependency, which resulted in our APIs receiving increased exceptions and errors. The issue was resolved once the external outage ended and normal service resumed.\n\n### Impact\n\nCustomers were unable to successfully complete requests through affected entitlements APIs for approximately two hours. This resulted in failed attempts to consume entitlements, impacting the user experience for games relying on these APIs.\n\n### Root Cause Analysis\n\nThe root cause of the incident was an external issue: a service outage in a third-party dependency. As our APIs depend on calls to the external service for authentication and entitlement verification, the outage led to increased exceptions and errors being returned to our services.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n* Enhanced our monitoring and alerting systems to provide earlier detection of external partner outages affecting entitlements APIs.\n\n* Reviewed and improved our exception handling and error messaging to ensure clear communication to customers when third-party outages impact API availability.",
507
  "first_seen": "2026-09-04T07:06:16Z",
508
  "impact": "major",
509
+ "last_seen": "2026-09-04T14:19:03Z",
510
  "resolved_at": "2025-10-09T14:40:12.926-07:00",
511
  "resolved_inferred": false,
512
  "started_at": "2025-10-09T12:54:59.999-07:00",
 
519
  "body": "On September 16, 2025, between 8:20 PM and 10:42 PM PDT, some customers experienced issues with PlayFab Lobbies. During this period, players across all titles using Lobbies were unable to create, join, or update lobbies, although search APIs remained functional. The incident was caused by a maintenance event internal to our Redis infrastructure, which disrupted connectivity between the Lobby service and Redis. We resolved the issue by rebooting the Redis instances, restoring connectivity and service functionality.\n\n### Impact\n\nPlayers were unable to create, join, or update lobbies across all titles that use the PlayFab Lobby system for approximately 2 hours and 22 minutes. While search APIs continued to work, players could not join lobbies they found during this time.\n\n### Root Cause Analysis\n\nThe root cause of the incident was a maintenance event within our Redis infrastructure that unexpectedly killed connectivity for the Lobby service. While we have the capability to schedule maintenance, this event occurred exactly when the impact started, leading to the service disruption.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n* Updated the Lobby service to better display its status on our service overview dashboard, which will enhance visibility and expedite future detection and mitigation efforts.\n\n* Improved our internal processes for scheduling and communicating maintenance events that could impact service connectivity.",
520
  "first_seen": "2026-09-04T07:06:16Z",
521
  "impact": "major",
522
+ "last_seen": "2026-09-04T14:19:03Z",
523
  "resolved_at": "2025-09-16T22:35:42.967-07:00",
524
  "resolved_inferred": false,
525
  "started_at": "2025-09-16T21:01:00.561-07:00",
 
532
  "body": "On September 12, 2025, between 01:42 AM and 03:09 AM PDT, some PlayFab customers experienced issues authenticating with Photon APIs. The incident was caused by unexpected traffic patterns to Photon API endpoints, which resulted in a hot partition and degraded availability. We resolved the issue by setting a throttle limit for the affected API endpoint.\n\n### Impact\n\nDuring the incident, customers with Photon tokens stored on the hot partition may have been unable to authenticate. The availability for Photon APIs dropped to as low as 78.8%, impacting service reliability for approximately 1 hour and 27 minutes.\n\n### Root Cause Analysis\n\nThe root cause was an unexpected traffic pattern on the Photon authentication API endpoint. A large call volume on this endpoint put strain on database lookup tables for logging in the user. The call volume was outside normal parameters.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Cached results from previous Photon sessions to reduce strain on the database infrastructure.\n\n\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Adjusted the title rate limit for the Photon APIs.",
533
  "first_seen": "2026-09-04T07:06:16Z",
534
  "impact": "minor",
535
+ "last_seen": "2026-09-04T14:19:03Z",
536
  "resolved_at": "2025-09-12T03:19:40.781-07:00",
537
  "resolved_inferred": false,
538
  "started_at": "2025-09-12T02:39:40.492-07:00",
 
545
  "body": "This incident has been resolved. All impacted scorecards are regenerated.",
546
  "first_seen": "2026-09-04T07:06:16Z",
547
  "impact": "minor",
548
+ "last_seen": "2026-09-04T14:19:03Z",
549
  "resolved_at": "2025-09-10T09:24:19.925-07:00",
550
  "resolved_inferred": false,
551
  "started_at": "2025-09-09T16:28:19.923-07:00",
 
558
  "body": "This incident has been resolved. Impact was observed from 20:40 PDT to 21:30 PDT. Note that this was after the previous related incident.",
559
  "first_seen": "2026-09-04T07:06:16Z",
560
  "impact": "major",
561
+ "last_seen": "2026-09-04T14:19:03Z",
562
  "resolved_at": "2025-09-01T11:09:03.144-07:00",
563
  "resolved_inferred": false,
564
  "started_at": "2025-08-31T20:40:49.000-07:00",
 
571
  "body": "On August 31, 2025, between 11:50 AM and 7:53 PM PDT, some customers experienced a complete outage of PlayFab Matchmaking. The incident was caused by a regression in the authentication library, which led to unexpected high call rates to Entra ID for token acquisition, resulting in service throttling and failures. We resolved the issue by increasing authentication rate limits, updating the authentication code, recycling affected application instances, and isolating impacted titles into dedicated deployments.\n\n### Impact\n\nDuring the outage, matchmaking services were unavailable for all affected titles, preventing players from joining matches. Notification failures also occurred, resulting in players being stuck in matchmaking and not receiving proper updates.\n\n### Root Cause Analysis\n\nThe root cause of the incident was a regression in the updated authentication library, which failed to cache tokens as expected. This led to a surge in token requests to Entra ID, causing throttling and authentication failures across the service. The updated library created new instances for each authentication attempt, breaking the caching mechanism and increasing network traffic unexpectedly.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n* Implemented service-level caching for authentication tokens to reduce unnecessary external calls.\n* Enhanced monitoring and diagnostics to detect abnormal network patterns and authentication failures more quickly.\n* Improved notification handling and recycling processes to prevent players from being stuck in matchmaking.",
572
  "first_seen": "2026-09-04T07:06:16Z",
573
  "impact": "major",
574
+ "last_seen": "2026-09-04T14:19:03Z",
575
  "resolved_at": "2025-08-31T20:28:48.383-07:00",
576
  "resolved_inferred": false,
577
  "started_at": "2025-08-31T12:00:46.000-07:00",
 
584
  "body": "On August 19, 2025, between 9:32 AM and 10:50 AM PDT, some customers experienced failures when calling PlayFab APIs due to issues with entity token validation. The incident was caused by a switch in the JSON library used for serialization and deserialization of entity tokens \\(for improved security and efficiency\\). We resolved the issue by rolling back the serialization change and advising impacted customers to refresh their tokens.\n\n### Impact\n\nDuring the incident, calls to validate entity tokens failed, preventing all further API calls using those tokens. Affected APIs primarily included WriteTelemetryEvents, Catalog search, GetPlayFabIdFrom\\*Id, ExecuteCloudScript, and Group-related APIs. This resulted in service disruption for customers relying on these endpoints.\n\n### Root Cause Analysis\n\nThe root cause was a deployment that switched the JSON library responsible for entity token serialization. After rolling back the change, errors persisted for tokens minted during the incident window, requiring customers to refresh their tokens.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n* Added documentation to the entity token release process to highlight serialization risks and warnings.\n\n* Implemented additional backcompat token tests for the entity token to expand test",
585
  "first_seen": "2026-09-04T07:06:16Z",
586
  "impact": "major",
587
+ "last_seen": "2026-09-04T14:19:03Z",
588
  "resolved_at": "2025-08-19T13:44:55.608-07:00",
589
  "resolved_inferred": false,
590
  "started_at": "2025-08-19T09:30:18.000-07:00",
 
597
  "body": "This incident has been resolved.",
598
  "first_seen": "2026-09-04T07:06:16Z",
599
  "impact": "none",
600
+ "last_seen": "2026-09-04T14:19:03Z",
601
  "resolved_at": "2025-08-14T15:11:19.249-07:00",
602
  "resolved_inferred": false,
603
  "started_at": "2025-08-14T14:15:26.000-07:00",
 
610
  "body": "On August 8, 2025, between 10:55 PM and 1:15 AM PDT, some customers experienced errors and delays when searching or purchasing catalog items through PlayFab\u2019s APIs. The incident was caused by a faulty service configuration intended for experimentation in a single region, which was mistakenly deployed to all regions due to human error. This misconfiguration led to increased internal server errors and service unavailability. The issue was resolved by rolling back the faulty configuration and confirming service recovery through monitoring and health checks.\n\n### Impact\n\nApproximately 12,000 players were affected, unable to search or purchase catalog items. During the outage, the latency of Catalog APIs \\(particularly SearchItems and GetItems\\) increased significantly, and many requests were rejected with a \u201cService unavailable\u201d status.\n\n### Root Cause Analysis\n\nThe root cause was a human error in deploying a service configuration intended for limited traffic in a single region. Instead, the configuration update was applied to all regions, increasing resource pressure and causing a spike in internal server errors for Catalog APIs dependent on storage. This led to widespread request failures and degraded service availability.\n\n### Action Items\n\n* Rolled back the faulty service configuration to restore normal operation.\n* Improved deployment validation procedures to ensure experimental changes are restricted to intended regions.\n* Enhanced monitoring and alerting systems to detect and report anomalies in API error rates and service health more rapidly.",
611
  "first_seen": "2026-09-04T07:06:16Z",
612
  "impact": "none",
613
+ "last_seen": "2026-09-04T14:19:03Z",
614
  "resolved_at": "2025-08-08T21:00:00.000-07:00",
615
  "resolved_inferred": false,
616
  "started_at": "2025-08-08T21:00:00.000-07:00",
 
623
  "body": "On July 31, 2025, between 10:30 AM and 7:29 PM PDT, some customers experienced significant delays when using PlayStream actions for rules and segments. Action executions were delayed, with a maximum delay of over 500 minutes at peak. The incident was caused by a combination of load and configuration values for the maximum number of records each processor could read at once, which, combined with pod health logic, led to excessive memory usage and processor failures. We resolved the issue by reducing the configuration value, which restored healthy processing across all partitions.\n\n### Impact\n\nAll PlayFab titles using PlayStream actions for rules and segments were impacted. Action executions were delayed but not dropped; however, the prolonged delay meant that some actions may not have been useful by the time they were processed.\n\n### Root Cause Analysis\n\nThe incident was caused by a misconfiguration in the number of records each processor attempted to read, combined with a change in the logic for partition allocation per processor. As processor pods failed due to memory exhaustion, the remaining healthy pods became overloaded, leading to a cascading failure and increasing delays in action processing.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n* We reduced the maximum number of records each processor can read at once, improving processor reliability and preventing memory exhaustion.\n* We improved our monitoring and alerting to detect abnormal processor delays and memory usage earlier.",
624
  "first_seen": "2026-09-04T07:06:16Z",
625
  "impact": "minor",
626
+ "last_seen": "2026-09-04T14:19:03Z",
627
  "resolved_at": "2025-07-31T21:55:03.196-07:00",
628
  "resolved_inferred": false,
629
  "started_at": "2025-07-31T15:17:00.765-07:00",
api/v/playvox.json CHANGED
@@ -3,7 +3,7 @@
3
  "slug": "playvox",
4
  "platform": "statuspage",
5
  "status_url": "https://status.playvox.com",
6
- "last_checked": "2026-09-04T12:24:18Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
@@ -12,7 +12,7 @@
12
  "body": "Our cloud provider has confirmed a full recovery of the service. We have continued monitoring and can confirm that Playvox services are operating normally at this time.\n\nThis incident is now considered resolved. If you experience any further issues, please don\u2019t hesitate to reach out.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
- "last_seen": "2026-09-04T12:24:18Z",
16
  "resolved_at": "2026-02-10T14:54:57.619-08:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-02-10T14:22:42.343-08:00",
@@ -25,7 +25,7 @@
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "none",
28
- "last_seen": "2026-09-04T12:24:18Z",
29
  "resolved_at": "2025-10-20T15:57:00.465-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2025-10-20T06:15:21.588-07:00",
 
3
  "slug": "playvox",
4
  "platform": "statuspage",
5
  "status_url": "https://status.playvox.com",
6
+ "last_checked": "2026-09-04T14:19:03Z",
7
  "last_state": "ok",
8
  "history_backfilled": true,
9
  "first_watched": "2026-09-04T07:06:16Z",
 
12
  "body": "Our cloud provider has confirmed a full recovery of the service. We have continued monitoring and can confirm that Playvox services are operating normally at this time.\n\nThis incident is now considered resolved. If you experience any further issues, please don\u2019t hesitate to reach out.",
13
  "first_seen": "2026-09-04T07:06:16Z",
14
  "impact": "minor",
15
+ "last_seen": "2026-09-04T14:19:03Z",
16
  "resolved_at": "2026-02-10T14:54:57.619-08:00",
17
  "resolved_inferred": false,
18
  "started_at": "2026-02-10T14:22:42.343-08:00",
 
25
  "body": "This incident has been resolved.",
26
  "first_seen": "2026-09-04T07:06:16Z",
27
  "impact": "none",
28
+ "last_seen": "2026-09-04T14:19:03Z",
29
  "resolved_at": "2025-10-20T15:57:00.465-07:00",
30
  "resolved_inferred": false,
31
  "started_at": "2025-10-20T06:15:21.588-07:00",