All Systems Operational

About This Site

Status page of the services that Reply.ai provides

US region (reply.ai) Operational
API Operational
Web App Operational
Message delivery Operational
Analytics Operational
Japan Region (transcosmos.reply.ai) Operational
API Operational
Web App Operational
Message delivery Operational
Analytics Operational
Service providers Operational
AWS ec2-ap-northeast-1 Operational
AWS ec2-us-east-1 Operational
AWS cloudFront Operational
AWS elb-ap-northeast-1 Operational
AWS elb-us-east-1 Operational
AWS rds-ap-northeast-1 Operational
AWS rds-us-east-1 Operational
AWS s3-ap-northeast-1 Operational
Heroku Operational
Redis Labs AWS/us-east.mz.1 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
Overall Application Performance Index ?
Fetching
Japan Region Send/Receive Message Roundtrip (Beta) ?
Fetching
Past Incidents
May 21, 2019
Platform release
Completed - The scheduled maintenance has been completed.
May 21, 09:17 EDT
Update - Release process is complete and platform is know stable
May 21, 09:17 EDT
Verifying - Verification is currently underway for the maintenance items.
May 21, 07:34 EDT
In progress - Release is currently being deployed.
May 21, 06:02 EDT
Update - We will be undergoing scheduled maintenance during this time.
May 21, 06:01 EDT
Scheduled - We will be undergoing a platform release during this time. Application and messaging may be unavailable.
May 21, 06:00 EDT
May 20, 2019

No incidents reported.

May 19, 2019

No incidents reported.

May 18, 2019

No incidents reported.

May 17, 2019
Chatbot responses are being delayed
Resolved - The issue has been solved. No message has been lost. Sorry for the inconvenience.
May 17, 19:00 EDT
Update - This is major outage on Heroku, part of Salesforce.

We are very sorry for the inconvenience.

Real-time updates:
- https://twitter.com/search?q=https%3A%2F%2Fstatus.salesforce.com%2Fincidents%2F3815&src=typd
- https://status.salesforce.com/incidents/3815
May 17, 16:18 EDT
Identified - Heroku, our infrastructure provider, is reporting a "Connect Delayed Synchronization". As a consequence, chatbots are not able to send any responses to end users at this moment. They are queued up and ready, and will be sent out as soon as Heroku clears this issue on their end. See https://status.heroku.com/incidents/1778 for more information.
May 17, 15:41 EDT
May 16, 2019

No incidents reported.

May 15, 2019

No incidents reported.

May 14, 2019

No incidents reported.

May 13, 2019

No incidents reported.

May 12, 2019

No incidents reported.

May 11, 2019

No incidents reported.

May 10, 2019

No incidents reported.

May 9, 2019

No incidents reported.

May 8, 2019

No incidents reported.

May 7, 2019

No incidents reported.

← Incident History Powered by Statuspage