Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Postcode Service kesinti geçmişi

    7 Postcode Service incidents · Mart 2018 — official updates, affected components, duration and resolution details.

    Güncel duruma dön

    Outage in Madrid & Oslo

    Başlangıç 26 Nisan 2021 09:45 UTC · 0m

    Pending
    Etkilenen bileşenler
    API postcode.tig.nl (end-of-life v3)
    1. 26 Nisan 2021 09:45 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

    Başlangıç 23 Mart 2021 17:32 UTC · 0m

    Pending
    1. 23 Mart 2021 17:33 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

    Başlangıç 14 Mart 2021 13:30 UTC · 0m

    Pending
    1. 14 Mart 2021 14:19 UTCresolved

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

    Degraded performance

    Başlangıç 19 Temmuz 2020 16:00 UTC · 0m

    OutageBüyük çaplı olay
    1. 23 Kasım 2020 16:50 UTCresolved

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

    Timeout

    Başlangıç 17 Temmuz 2020 13:30 UTC · 0m

    IssuesKüçük çaplı olay
    1. 23 Kasım 2020 16:59 UTCresolved

      We received timeouts from Germany and Italy to our service.

    Cannot make SSL connection

    Başlangıç 26 Mayıs 2020 21:00 UTC · 0m

    OutageKritik olay
    1. 23 Kasım 2020 17:05 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

    Başlangıç 19 Mart 2018 08:59 UTC · 5h 11m

    Pending
    1. 19 Mart 2018 08:59 UTCidentified

      Investigating reported issues with whitelisted IP clients.

    2. 19 Mart 2018 09:23 UTCmonitoring

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

    3. 19 Mart 2018 14:10 UTCresolved

      This incident has been resolved.