BufferIssue Publishing Posts to TikTok
The issue with TikTok posts has been fully resolved, and all systems are now operational. We appreciate your understanding and apologise for any disruption this may have caused.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
The issue with TikTok posts has been fully resolved, and all systems are now operational. We appreciate your understanding and apologise for any disruption this may have caused.
Resolved
The maintenance has been completed successfully. All systems are operational. Affected IMSI5 customers should see connectivity restored automatically. If you are still experiencing issues, please toggle airplane mode on your device for 10 seconds and then off.
Resolved
Duplicate incident - please disregard.
Resolved
This incident has been resolved.
Resolved
Issue has been resolved, everything is operational.
Resolved
All affected customers should now have received their credits. We sincerely apologize for the inconvenience this caused and appreciate your patience throughout. If you have any questions or are still experiencing issues related to this, please don't hesitate to reach out to our support team.
Resolved
All impacted services have now fully recovered.
Resolved
We experienced elevated 5xx errors with our help center product between 05.43 UTC to 06.04 UTC. The issue has been resolved and all functionality should be back to normal. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour.
Resolved
We experienced elevated 5xx errors with our help center product between 05.43 UTC to 06.04 UTC. The issue has been resolved and all functionality should be back to normal. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour.
Resolved
We experienced elevated 5xx errors with our help center product between 05.43 UTC to 06.04 UTC. The issue has been resolved and all functionality should be back to normal. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour.
Resolved
This incident has been resolved.
Resolved
The issues causing increased error rates in the US East region have been resolved.
Resolved
TLDR: A production upgrade for Monolithdb from version 8.0.40 to 8.4.8 is currently resolved now and everything is functional. All systems are back to normal
Resolved
This incident has been resolved
Resolved
This incident has been resolved.
Resolved
This incident has been resolved. All Dashboard and Terminus operations are operational now.
Resolved
Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0154019](https://community.snowflake.com/s/article/INC0154019)
Resolved
We think the impact from the issue is over.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue with TikTok posts has been fully resolved, and all systems are now operational. We appreciate your understanding and apologise for any disruption this may have caused.
Resolved
This incident has been resolved.
Resolved
Indicators are pointing to a healthy state now after the fix. Everything should be operating well.
Resolved
We have confirmed that project creation has returned to normal.
Resolved
On March 27, 2026, from 02:30 to 04:56 UTC, a misconfiguration in our rate limiting system caused users on Copilot Free, Student, Pro, and Pro+ plans to experience unexpected rate limit errors. The configuration that was incorrectly applied was intended solely for internal staff testing of rate-limiting experiences. Copilot Business and Copilot Enterprise accounts were not affected. During this period, affected users received error messages instructing them to retry after a certain time. Approximately 32% of active Free users, 35% of active Student users, 46% of active Pro users, and 66% of active Pro+ users were affected. After identifying the root cause, we reverted the change and restored the expected rate limits. We are reviewing our deployment and validation processes to help ensure configurations used for internal testing cannot be inadvertently applied to production environments.
Resolved
This issue has been resolved.
Resolved
At about 3:00pm PST on 3/26/2026 the Lever Support Team triggered a data operation job through an internal admin interface. The data required for this job did not have sufficient database indexes available on the server which caused significant strain on the database servers. The result of this caused site degradation and failed page loads for hire.lever.co between 3:04pm - 3:26pm PST. Impacted users would notice a "500 error" during the affected page loads. Service was restored to all users as of 3:26pm PST. Following this time we continued to optimize the databases for the intended data operation. Full functionality was reached at about 10:00pm PST.
Resolved
Our engineers implemented a fix for this issue and have confirmed no further impact.
Resolved
This issue has been fully resolved. Publishing is working as normal and all previously affected projects are now displaying their most recent publish correctly
Resolved
This incident has been resolved.
Resolved
Anthropic API recovered for more than 1h. Customers on free and core plans won't be impacted anymore.
Resolved
From 16:30 UTC, we observed increased errors for Edge Function invocations on the Standard Edge Network. This includes framework generated Edge Functions like Next.js Middleware. The issue has been resolved as of 16:52 UTC.
Resolved
The LLM-as-a-Judge delays on HIPPA data region have now been resolved. We will continue to monitor the situation.
Resolved
We have fixed the issue
Resolved
Some Flags and experiments that were targeting cohorts did not evaluate users into control and treatment correctly. This has been fixed
Resolved
Due to a race condition in a process that attaches static IPs to nodes, some of the IPs in the dns were detached from the nodes, causing timeouts.
Resolved
Log ingestion has returned to normal
Resolved
This incident has been resolved.
Resolved
We have resolved the issue.
Resolved
We are no longer seeing intermittent spikes in HTTP 503 errors.
Resolved