{
"vendor": "Aptible",
"slug": "aptible",
"platform": "statuspage",
"status_url": "https://status.aptible.com",
"last_checked": "2026-09-16T12:28:20Z",
"last_state": "ok",
"history_backfilled": true,
"first_watched": "2026-09-04T07:06:16Z",
"incidents": [
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-27T11:12:00.684-04:00",
"resolved_inferred": false,
"started_at": "2026-07-27T06:31:04.452-04:00",
"state": "resolved",
"title": "Operation failures due to AWS Outage",
"updated_at": "2026-07-27T11:12:00.701-04:00",
"url": "https://stspg.io/yhdbrjtcvdry"
},
{
"body": "Following the fixes deployed per the previous update, we have seen stable performance on the LLM Gateway since 7:12 EDT and are resolving the issue.\n\nThe root cause of this issue was a severe performance degradation in 3 specific endpoints:\n\u2022\u00a0`GET /models`\n\u2022\u00a0`GET /v1/models`\n\u2022\u00a0`GET /metadata/models`\n\n...all of which return a list of available models. The performance issue on these endpoints was severe enough to cause significant request queueing and degraded performance for other unaffected endpoints. The fix we deployed added caching on this endpoint to ensure fast responses. Since those fixes have been deployed, we are no longer seeing request queueing or impacts to other LLM Gateway API endpoints.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-17T13:04:04.670-04:00",
"resolved_inferred": false,
"started_at": "2026-07-16T18:31:08.575-04:00",
"state": "resolved",
"title": "Delayed and Timed-out requests to the Aptible LLM Gateway",
"updated_at": "2026-07-17T13:04:04.687-04:00",
"url": "https://stspg.io/fgcj33x9gr8v"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-23T17:48:13.568-04:00",
"resolved_inferred": false,
"started_at": "2026-06-08T14:28:46.841-04:00",
"state": "resolved",
"title": "Security Patching of Systemd Vulnerabilities",
"updated_at": "2026-06-23T17:48:13.583-04:00",
"url": "https://stspg.io/4zrvlp4thtcd"
},
{
"body": "As of 18:42 UTC the upstream provider began to accept log messages again consistently and this issue is now remediated.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-03T15:16:20.104-04:00",
"resolved_inferred": false,
"started_at": "2026-06-03T12:02:30.705-04:00",
"state": "resolved",
"title": "Partial Service Degradation with Mezmo Log Drains",
"updated_at": "2026-06-03T15:16:20.119-04:00",
"url": "https://stspg.io/j7r65mwxr2tn"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-08T11:35:02.686-04:00",
"resolved_inferred": false,
"started_at": "2026-05-08T01:02:07.845-04:00",
"state": "resolved",
"title": "Aptible response to CVE-2026-43284",
"updated_at": "2026-05-08T11:35:02.700-04:00",
"url": "https://stspg.io/n215dy50hrrs"
},
{
"body": "An upstream AWS issue affected infrastructure in a single Availability Zone in us-east-1. During the event, we blocked provisioning into the affected zone and monitored AWS\u2019s recovery efforts.\n\nAWS has since recovered enough of the affected availability zone for the impacted Aptible infrastructure to recover. We have also completed recovery of any Aptible-managed resources that required follow-up action on our side.\n\nAny customers with directly affected resources have been notified of resolution. We are continuing normal platform monitoring, but we are marking this incident as resolved on our end.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-08T23:35:54.117-04:00",
"resolved_inferred": false,
"started_at": "2026-05-07T21:05:42.870-04:00",
"state": "resolved",
"title": "Instability in us-east-1",
"updated_at": "2026-05-08T23:35:54.132-04:00",
"url": "https://stspg.io/kmx5y0gf08fg"
},
{
"body": "Aptible is aware of CVE-2026-31431, also known as \u201cCopy Fail,\u201d a recently disclosed Linux kernel vulnerability that may allow local privilege escalation under certain conditions [0].\n\nWe have taken action across the Aptible platform to protect all customer workloads against this vulnerability. No customer action is required at this time.\n\nWe will continue to monitor upstream kernel, distribution, and security vendor guidance related to this CVE and will take any additional action if needed.\n\n[0] https://copy.fail/",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-29T18:40:43.316-04:00",
"resolved_inferred": false,
"started_at": "2026-04-29T18:40:43.273-04:00",
"state": "resolved",
"title": "Aptible response to CVE-2026-31431",
"updated_at": "2026-04-29T18:40:43.327-04:00",
"url": "https://stspg.io/p5q6dvc5wrtj"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-18T23:10:17.839-04:00",
"resolved_inferred": false,
"started_at": "2026-04-18T22:03:58.794-04:00",
"state": "resolved",
"title": "Service degradation affecting api.aptible.com",
"updated_at": "2026-04-18T23:10:17.855-04:00",
"url": "https://stspg.io/0rm59lr8vytq"
},
{
"body": "Additional detail about timeline: we observed a relative increase in DNS resolver errors in us-east-1 beginning at approximately 2026-03-17 18:30 UTC. The elevated error rate was intermittent rather than constant, with the most visible clusters occurring from roughly 18:30-18:55 UTC and again from about 20:55-21:40 UTC. Error rates returned to normal shortly after 21:40 UTC.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-17T19:33:35.883-04:00",
"resolved_inferred": false,
"started_at": "2026-03-17T18:33:47.740-04:00",
"state": "postmortem",
"title": "us-east-1 Intermittent DNS Resolution Errors",
"updated_at": "2026-03-18T12:50:55.333-04:00",
"url": "https://stspg.io/hbcgtg23jxjl"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-31T09:49:00.737-05:00",
"resolved_inferred": false,
"started_at": "2025-12-31T05:48:35.671-05:00",
"state": "resolved",
"title": "Performance issues on auth.aptible.com",
"updated_at": "2025-12-31T09:49:00.755-05:00",
"url": "https://stspg.io/hxt1tmldyt0h"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-30T12:15:34.065-05:00",
"resolved_inferred": false,
"started_at": "2025-12-29T21:14:23.204-05:00",
"state": "resolved",
"title": "CVE-2025-14847: MongoDB unauthenticated information leak",
"updated_at": "2025-12-30T12:15:34.082-05:00",
"url": "https://stspg.io/0pk4mdw80g97"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-08T11:52:22.240-05:00",
"resolved_inferred": false,
"started_at": "2025-12-05T09:39:55.817-05:00",
"state": "resolved",
"title": "CVE-2025-55182: React server component vulnerability",
"updated_at": "2025-12-08T11:52:22.260-05:00",
"url": "https://stspg.io/fgzksnqqdt6d"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-05T11:07:49.146-05:00",
"resolved_inferred": false,
"started_at": "2025-11-05T10:59:59.035-05:00",
"state": "resolved",
"title": "Platform API Performance Degradation",
"updated_at": "2025-11-05T11:07:49.165-05:00",
"url": "https://stspg.io/x01bzf3pzdys"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-29T17:50:27.460-04:00",
"resolved_inferred": false,
"started_at": "2025-10-29T17:17:17.088-04:00",
"state": "resolved",
"title": "Operations Impacted by Host Provisioning Failures",
"updated_at": "2025-10-29T17:50:27.480-04:00",
"url": "https://stspg.io/9pg6fj55hwr8"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-28T17:08:52.592-04:00",
"resolved_inferred": false,
"started_at": "2025-10-28T13:09:06.240-04:00",
"state": "resolved",
"title": "Delays and failures for provisioning-related operations in us-east-1",
"updated_at": "2025-10-28T17:08:52.606-04:00",
"url": "https://stspg.io/g96sgtv03wr8"
},
{
"body": "AWS has marked the underlying issue in us-east-1 as resolved, and we\u2019ve confirmed continued stability across all EC2-related operations.\n\nAll Aptible operations are functioning normally, and this incident is now closed.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-20T19:04:19.807-04:00",
"resolved_inferred": false,
"started_at": "2025-10-20T07:53:09.171-04:00",
"state": "resolved",
"title": "Operation failures due to AWS Outage",
"updated_at": "2025-10-20T19:04:20.179-04:00",
"url": "https://stspg.io/y2hhdtzd51p5"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-20T05:46:00.046-04:00",
"resolved_inferred": false,
"started_at": "2025-10-20T03:47:14.947-04:00",
"state": "resolved",
"title": "Operation failures to to AWS API incident",
"updated_at": "2025-10-20T05:46:00.419-04:00",
"url": "https://stspg.io/rm2t1b3th5m9"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-11T23:40:31.265-04:00",
"resolved_inferred": false,
"started_at": "2025-10-11T22:30:16.257-04:00",
"state": "resolved",
"title": "Delays and queued operations in us-east-1",
"updated_at": "2025-10-11T23:40:31.282-04:00",
"url": "https://stspg.io/2709j0rps1fx"
},
{
"body": "Aptible has reviewed and addressed the Redis vulnerability described in <a href=\"https://redis.io/blog/security-advisory-cve-2025-49844/\" target=\"_blank\">https://redis.io/blog/security-advisory-cve-2025-49844/</a>.\n\nWe have confirmed that all internal Redis instances used in delivering the Aptible platform are secure and have no exploitation path related to this CVE.\n\nFor Aptible customers who do not have their Redis databases publicly exposed, a path to exploitation is similarly unlikely. Additionally, for customers using Redis 6.2 databases on Aptible, a patched version will be available by Oct 10th at 5pm EST, and additional releases (7.2) are upcoming; see <a href=\"https://www.aptible.com/changelog/\" target=\"_blank\">aptible.com/changelog</a> for ongoing release updates. To ensure you are running the latest minor version when available, please run the cli command: aptible db:reload for each Redis database.\n\nFor more information on using this command, visit <a href=\"https://www.aptible.com/docs/reference/aptible-cli/cli-commands/cli-db-reload\" target=\"_blank\">https://www.aptible.com/docs/reference/aptible-cli/cli-commands/cli-db-reload</a>.\n\nIf you have any specific questions or concerns related to this CVE, please <a href=\"https://contact.aptible.com/\" target=\"_blank\">contact us</a>.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-10T11:53:25.000-04:00",
"resolved_inferred": false,
"started_at": "2025-10-10T11:53:25.000-04:00",
"state": "resolved",
"title": "Redis Security Advisory (CVE-2025-49844)",
"updated_at": "2025-10-10T12:25:20.338-04:00",
"url": "https://stspg.io/n4ktsr6w1cwg"
}
]
}