Incidents History
-
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.