Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Postcode Service 中断历史

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

    返回当前状态

    Outage in Madrid & Oslo

    开始时间 2021年4月26日 UTC 09:45 · 0m

    Pending
    受影响的组件
    API postcode.tig.nl (end-of-life v3)
    1. 2021年4月26日 UTC 09:45resolved

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

    Outage in datacenter AMS

    开始时间 2021年3月23日 UTC 17:32 · 0m

    Pending
    1. 2021年3月23日 UTC 17:33resolved

      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

    开始时间 2021年3月14日 UTC 13:30 · 0m

    Pending
    1. 2021年3月14日 UTC 14:19resolved

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

    Degraded performance

    开始时间 2020年7月19日 UTC 16:00 · 0m

    Outage重大事件
    1. 2020年11月23日 UTC 16:50resolved

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

    Timeout

    开始时间 2020年7月17日 UTC 13:30 · 0m

    Issues轻微事件
    1. 2020年11月23日 UTC 16:59resolved

      We received timeouts from Germany and Italy to our service.

    Cannot make SSL connection

    开始时间 2020年5月26日 UTC 21:00 · 0m

    Outage严重事件
    1. 2020年11月23日 UTC 17:05resolved

      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

    开始时间 2018年3月19日 UTC 08:59 · 5h 11m

    Pending
    1. 2018年3月19日 UTC 08:59identified

      Investigating reported issues with whitelisted IP clients.

    2. 2018年3月19日 UTC 09:23monitoring

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

    3. 2018年3月19日 UTC 14:10resolved

      This incident has been resolved.