Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Postcode Service outage history

    7 recorded Postcode Service incidents since March 2018, with official updates, affected components, duration and resolution information.

    Back to current status

    Outage in Madrid & Oslo

    Started April 26, 2021 at 9:45 AM UTC · 0m

    Pending
    Affected components
    API postcode.tig.nl (end-of-life v3)
    1. April 26, 2021 at 9:45 AM UTCresolved

      This incident has been solved. There was a socket timeout from Madrid and Oslo, duration was less than 1 minute.

    Outage in datacenter AMS

    Started March 23, 2021 at 5:32 PM UTC · 0m

    Pending
    1. March 23, 2021 at 5:33 PM UTCresolved

      There was an outage in the datacenter of our hoster AMS-3 affecting all service. The service is operational again. We are investigating the cause of the outage with the hosting provider.

    Degraded performance

    Started March 14, 2021 at 1:30 PM UTC · 0m

    Pending
    1. March 14, 2021 at 2:19 PM UTCresolved

      Connectivity issues from Sweden, Spain and Germany to our service caused by the infrastructure of our hoster.

    Degraded performance

    Started July 19, 2020 at 4:00 PM UTC · 0m

    OutageMajor incident
    1. November 23, 2020 at 4:50 PM UTCresolved

      We received reports from Germany and Italy to our service. We have investigated the incidents and found a routing bottleneck.

    Timeout

    Started July 17, 2020 at 1:30 PM UTC · 0m

    IssuesMinor incident
    1. November 23, 2020 at 4:59 PM UTCresolved

      We received timeouts from Germany and Italy to our service.

    Cannot make SSL connection

    Started May 26, 2020 at 9:00 PM UTC · 0m

    OutageCritical incident
    1. November 23, 2020 at 5:05 PM UTCresolved

      We have disabled TLS v1 in our nodes that caused temporarily connection issues when using HTTPS for a brief moment.

    Reported issues with whitelisted IP clients

    Started March 19, 2018 at 8:59 AM UTC · 5h 11m

    Pending
    1. March 19, 2018 at 8:59 AM UTCidentified

      Investigating reported issues with whitelisted IP clients.

    2. March 19, 2018 at 9:23 AM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. March 19, 2018 at 2:10 PM UTCresolved

      This incident has been resolved.