Header Image
All Systems Operational

Updated a few seconds ago

We continuously monitor our services. Any issues will be posted here.

api.sentilink.com




Operational

dashboard.sentilink.com




Operational

api.sandbox-sentilink.com




Operational

eCBSV




Operational

1

Upcoming Maintenances

2

Incidents Last 30 Days

1

Maintenances Last 30 Days

External Services

Amazon Web Services

Scheduled Maintenance

eCBSV Maintenance WindowPlanned Maintenance

Schedule

September 12, 2026 20:00 - September 13, 2026 00:00 PDT
September 13, 2026 03:00 - September 13, 2026 07:00 UTC

Components

eCBSV

Services

API

Description

On Saturday, September 12th, the Social Security Administration will be taking their mainframe services offline for maintenance. Maintenance is scheduled to begin at 11:00 PM PT (8:00 PM ET), and is expected to last approximately 4 hours. During this time, SentiLink will not be able to process eCBSV requests.

History (Last 7 days)

SentiLink - Server IssuesPartial Service Disruption

Incident Status

Partial Service Disruption


Components

api.sentilink.com


Services

API



September 8, 2026 12:24 PDT
September 8, 2026 19:24 UTC
INVESTIGATING

SentiLink is currently experiencing server issues resulting in HTTP 5XX status codes. We are actively investigating and working towards a resolution.

September 8, 2026 12:51 PDT
September 8, 2026 19:51 UTC
MONITORING

The issue has been identified and fixed. We're currently monitoring the situation and analyzing impact.

September 8, 2026 13:20 PDT
September 8, 2026 20:20 UTC
MONITORING

The partial outage occurred between 12:17-12:37pm PT and again between 1:06-1:08pm PT, causing a small volume of requests to fail with HTTP 5XX status codes. We've deployed a fix and are actively monitoring the situation to ensure it doesn't reoccur.

September 8, 2026 15:00 PDT
September 8, 2026 22:00 UTC
MONITORING

Services are operational and we are continuing to monitor to ensure server stability.

September 9, 2026 13:44 PDT
September 9, 2026 20:44 UTC
RESOLVED

Issue was resolved with the fix deployed at 1:09pm PT on September 8th.