All Systems Operational
API ? Operational
Public Web Portal ? Operational
Secure Web Portal ? Operational
Couriers Tracking System ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
api.aftership.com Uptime ?
Fetching
www.aftership.com Uptime ?
Fetching
Past Incidents
Jun 23, 2017

No incidents reported today.

Jun 22, 2017

No incidents reported.

Jun 21, 2017

No incidents reported.

Jun 20, 2017

No incidents reported.

Jun 19, 2017

No incidents reported.

Jun 18, 2017

No incidents reported.

Jun 17, 2017

No incidents reported.

Jun 16, 2017

No incidents reported.

Jun 15, 2017

No incidents reported.

Jun 14, 2017

No incidents reported.

Jun 13, 2017
Resolved - The API service with new instances are running properly.
Jun 13, 14:24 HKT
Monitoring - Between 2017-06-12 21:18 UTC and 2017-06-12 22:16 UTC, the API service was down. Meanwhile Secure Web Portal and Apps were affected as they were depending on the tracking API service. The issue was resolved and we keep monitoring the service.

Our API service is running with automatic scaling mechanism. During the incident, our system failed to allocate new instances automatically. Hence no service is available.

We have resolved the issue by changing the instance type manually and restart our API service. While instances are successfully allocated, the API services are resumed back to normal.

Technical details:
Our API service is running on Amazon Web Service (AWS) EC2 platform. It failed to allocate any EC2 instances automatically (instance type c3.xlarge, c4.xlarge, m3.xlarge, m4.xlarge) in AWS region "us-east-1" during the incident. We manually changed the instance type (c3.2xlarge and m4.2xlarge) and EC2 instances are successfully allocated.
Jun 13, 10:45 HKT
Jun 12, 2017

No incidents reported.

Jun 11, 2017

No incidents reported.

Jun 10, 2017

No incidents reported.

Jun 9, 2017

No incidents reported.