Mechanic's runtime is experiencing slightly spotty performance. Events are still being accepted, and will be processed as quickly as possible.
Apr 27, 00:08 UTC
Investigating -
Performance and availability is currently degraded. We're investigating.
Apr 27, 00:05 UTC
Resolved -
This incident has been resolved.
Apr 24, 21:28 UTC
Update -
Mechanic runtime performance is back to normal. Some stores are experiencing increased RTT times, due to store-specific Mechanic queues processing backlog from the incident period. These queues will recover normally, but please do email team@usemechanic.com if you've got questions. :)
We'll close this incident when Fly marks the incident closed on their end.
Update -
For clarity: Mechanic event ingress is unaffected, including submissions sent to https://webhooks.mechanic.dev/.
The Mechanic platform is still accepting all submitted events, and all events will be processed as soon as the Mechanic runtime is able to address them.
Apr 24, 19:03 UTC
Update -
Our infra provider has acknowledged the issue, and it's in their hands now:
Identified -
The Mechanic runtime is impacted by network issues occurring upstream. It appears to be at the level of our primary infrastructure provider; we're connecting with them to see what's what.
Apr 24, 18:54 UTC