Incidents History
-
Back office website Back office website - apcomp Back office website - oncomp Back office website - cicomp Back office website - lmcomp Back office website - secomp Websales Web Reports Accounts API Inventory API Trip Search API Notifications API Notifications Worker Operations API Payments API Reports API Reports worker Sales API Uploads API Coltrane API GPS API Internal API Invoices API Seatmaps API GTFS Worker Uploads worker Archiving worker Data import worker Expired referenced payments worker Exports worker GPS worker Manifest workermajor-outageWe have experienced an issue with the main db cluster caused by a deployment which affected the main database
-
Back office websitepartial-outageA bug was introduced affecting the functionality of sending emails on tickets purchase confirmation.
-
Back office websitepartial-outageThe deployment process did not push the needed files in the CDN source.
-
Back office websitepartial-outageSome instances started to go unhealthy or unresponsive around 5:45 Eastern time.
-
resolved
Partial issues accessing back-office
Back office websitepartial-outageSome instances started to go unhealthy or unresponsive around 5:45 Eastern time. -
resolved
Primary DB exhausted connections
Back office website Websales Calendar websales Accounts API Inventory API Trip Search API Loyalty API Notifications API Operations API Payments API Reports API Reports worker Sales API Webhooks workermajor-outageThe db cluster primary server exhausted all possible connections and services started to fail. -
Back office websitepartial-outageV8 garbage collection fired up in two servers in the server pool, causing some momentary 502 status responses in new requests.
-
Back office websitemajor-outageAt about 12:08 EDT the servers stopped responding for some customers.