2017-11-02: Service restored.

2017-11-02: Service restored.

Postby rkulagow » Thu Nov 02, 2017 8:18 pm

2017-11-03 @ 11:27 UTC / 2017-11-03 @ 6:37A CDT

Service has been restored.

2017-11-03 @ 01:24 / 2017-11-02 @ 8:24P CDT

We have disabled the "headends in a postal code" function in our code in order to partially restore service. Accessing the /headends REST endpoint will now return code 3001 in the JSON body of the response, with a HTTP 400. There will be an update to this message when our upstream has fully restored service and we have been able to confirm.

2017-11-03 @ 00:20UTC / 2017-11-02@7:20P CDT

Our upstream is still working on their issue; we are updating our code to allow for a restoration of service for existing customers; subscribers attempting to add lineups will still have issues until the upstream problem is resolved. Next update will be at 0200 UTC / 9P CDT.

2017-11-02 @ 19:10UTC / 2017-11-02@2:10P CDT

Due to an upstream API issue the service has been put into maintenance mode.
rkulagow
SD Staff
 
Posts: 893
Joined: Tue Aug 14, 2007 3:15 pm

Re: 2017-11-02: Service restored.

Postby rkulagow » Fri Nov 03, 2017 7:06 am

2017-11-03 @ 11:27 UTC / 2017-11-03 @ 6:37A CDT

Service has been restored.
rkulagow
SD Staff
 
Posts: 893
Joined: Tue Aug 14, 2007 3:15 pm


Return to Service Issues

Who is online

Users browsing this forum: No registered users and 1 guest

cron