{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihflk4zn4fyp5oad2uc43ph63lymhysznwyo3dshar2ribe7nih6u",
    "uri": "at://did:plc:gh6z6exaevczos7dupvzztts/app.bsky.feed.post/3ml2ybti5ejo2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiblq3wqbt5gewbqpvfd2dcif7lthr4xh6bn4ijrioze7qdcyvadm4"
    },
    "mimeType": "image/png",
    "size": 3910
  },
  "path": "/incidents/hj0flrrsq2z9",
  "publishedAt": "2026-05-04T19:57:16.000Z",
  "site": "https://status.ed.link",
  "textContent": "May  4, 19:57 UTC\n**Resolved** - We've identified the root cause and the pipeline has resumed. We will publish a full post-mortem shortly.\n\nMay  4, 18:30 UTC\n**Update** - We've isolated the issue to our sync service that retrieves data from school data sources. We are re-enabling enrichment & materialization. We are going to revert to the previous stable version of the sync application and re-enable it in a limited capacity for monitoring.\n\nMay  4, 18:16 UTC\n**Monitoring** - Reports of degraded API & SSO performance started coming in around 12:30pm CT.\nAfter investigation our logs, it appears that the degraded performance started at exactly 12:07pm Central Time (about 27 minutes prior to first reports).\nAs of 1:04pm Central Time, we have reallocated database resources and the immediate issue has been resolved. SSO & API requests have returned to expected levels.\nWe are continuing to investigate the root cause of the issue before restoring normal pipeline services.\n\nPlease expect delays in sync and materialization queues while we investigate the issue.",
  "title": "Degraded API Performance",
  "updatedAt": "2026-05-04T21:22:51.000Z"
}