<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <link rel="alternate" type="text/html" href="https://opalstackstatus.com/"/>
    <title>Singapore on Opalstack Status</title>
    <link>https://opalstackstatus.com/affected/singapore/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2024-05-31T11:45:00+00:00</lastBuildDate>
    <updated>2024-05-31T11:45:00+00:00</updated>
    
    
    
      <atom:link href="https://opalstackstatus.com/affected/singapore/index.xml" rel="self" type="application/rss+xml" />
    
    
      <item>
        <title>[Resolved] DNS outage (resolved)</title>
        <link>https://opalstackstatus.com/issues/2024-05-31-dns-outage-resolved/</link>
        <pubDate>Fri, 31 May 2024 11:45:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2024-05-31-dns-outage-resolved/</guid>
        <category>2024-05-31 14:52:45</category>
        <description>&lt;p&gt;About 1 hour ago a failed DNS sync with our alternate DNS provider caused an outage in our DNS servers. The outage lasted approximately 1 hour during which customers may have experience trouble accessing Opalstack systems.&lt;/p&gt;
&lt;p&gt;The problem has been resolved and all DNS services are working normally at this time, however there may be lingering effects due to global DNS propagation. These issues will resolve themselves over the next few hours. You may be able to resolve them sooner for yourself by &lt;a href=&#34;https://www.wikihow.com/Flush-DNS&#34;&gt;flushing your DNS&lt;/a&gt; and/or by power-cycling your devices. 
  &lt;span class=&#34;faded&#34;&gt;(11:45 UTC — May 31)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;About 1 hour ago a failed DNS sync with our alternate DNS provider caused an outage in our DNS servers. The outage lasted approximately 1 hour during which customers may have experience trouble accessing Opalstack systems.&lt;/p&gt;
&lt;p&gt;The problem has been resolved and all DNS services are working normally at this time, however there may be lingering effects due to global DNS propagation. These issues will resolve themselves over the next few hours. You may be able to resolve them sooner for yourself by &lt;a href=&#34;https://www.wikihow.com/Flush-DNS&#34;&gt;flushing your DNS&lt;/a&gt; and/or by power-cycling your devices. 
  &lt;span class=&#34;faded&#34;&gt;(11:45 UTC — May 31)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Delayed domain updates</title>
        <link>https://opalstackstatus.com/issues/2022-12-29-delayed-domain-updates/</link>
        <pubDate>Thu, 29 Dec 2022 02:21:36 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2022-12-29-delayed-domain-updates/</guid>
        <category>2022-12-29 04:48:35</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The backlog of domain updates is now clear. 
  &lt;span class=&#34;faded&#34;&gt;(04:48 UTC — Dec 29)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;At this time (Thu Dec 29 02:17:55 UTC 2022) there is a backlog of domain updates which are waiting to be deployed to our name servers. Customers who are affected by this will see domains listed as &amp;ldquo;Pending&amp;rdquo; in their Opalstack dashboards.&lt;/p&gt;
&lt;p&gt;The actual processing delay is on our Singapore name servers. If your domain is using the US or DE name servers then they&amp;rsquo;ll still appear as pending but the domains will actually be updated on the NS. Only domains that use the Singapore servers will actually be affected, and it&amp;rsquo;s only a small number at this time.&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The backlog of domain updates is now clear. 
  &lt;span class=&#34;faded&#34;&gt;(04:48 UTC — Dec 29)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;At this time (Thu Dec 29 02:17:55 UTC 2022) there is a backlog of domain updates which are waiting to be deployed to our name servers. Customers who are affected by this will see domains listed as &amp;ldquo;Pending&amp;rdquo; in their Opalstack dashboards.&lt;/p&gt;
&lt;p&gt;The actual processing delay is on our Singapore name servers. If your domain is using the US or DE name servers then they&amp;rsquo;ll still appear as pending but the domains will actually be updated on the NS. Only domains that use the Singapore servers will actually be affected, and it&amp;rsquo;s only a small number at this time.&lt;/p&gt;
&lt;p&gt;The cause of the issue appears to be network-related so we&amp;rsquo;re working with our upstream providers to resolve this.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll update this post when more information is available. 
  &lt;span class=&#34;faded&#34;&gt;(02:21 UTC — Dec 29)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Service disruption caused by firewall issue</title>
        <link>https://opalstackstatus.com/issues/2022-02-10-service-disruption-caused-by-firewall-issue/</link>
        <pubDate>Thu, 10 Feb 2022 19:43:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2022-02-10-service-disruption-caused-by-firewall-issue/</guid>
        <category>2022-02-10 19:48:19</category>
        <description>&lt;p&gt;About an hour ago we deployed a firewall update that had the unintended side effect of blocking our resolving DNS servers.&lt;/p&gt;
&lt;p&gt;This caused various issues on customer sites on shared hosting, usually showing up as a &amp;ldquo;504 Gateway Timeout&amp;rdquo; error.&lt;/p&gt;
&lt;p&gt;The issue has been resolved and all customer sites should be working now as they were prior to the change. 
  &lt;span class=&#34;faded&#34;&gt;(19:43 UTC — Feb 10)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;About an hour ago we deployed a firewall update that had the unintended side effect of blocking our resolving DNS servers.&lt;/p&gt;
&lt;p&gt;This caused various issues on customer sites on shared hosting, usually showing up as a &amp;ldquo;504 Gateway Timeout&amp;rdquo; error.&lt;/p&gt;
&lt;p&gt;The issue has been resolved and all customer sites should be working now as they were prior to the change. 
  &lt;span class=&#34;faded&#34;&gt;(19:43 UTC — Feb 10)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Connectivity issues in Singapore</title>
        <link>https://opalstackstatus.com/issues/2020-12-20-connectivity-issues-in-singapore/</link>
        <pubDate>Sun, 20 Dec 2020 11:00:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2020-12-20-connectivity-issues-in-singapore/</guid>
        <category>2020-12-21 18:21:42</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - Linode reports that the connectivity issues in Singapore have been resolved. 
  &lt;span class=&#34;faded&#34;&gt;(18:21 UTC — Dec 21)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - All Singapore servers are back online at this time. We&amp;rsquo;ll continue to monitor. 
  &lt;span class=&#34;faded&#34;&gt;(17:31 UTC — Dec 21)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - Linode are investigating a connectivity issue in our Singapore data center. During this time, users may experience connection timeouts and errors for all services deployed in this data center. We will share additional updates as we have more information: &lt;a href=&#34;https://status.linode.com/incidents/wfghw8md5j8k&#34;&gt;https://status.linode.com/incidents/wfghw8md5j8k&lt;/a&gt; 
  &lt;span class=&#34;faded&#34;&gt;(16:52 UTC — Dec 21)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - Linode reports that the connectivity issues in Singapore have been resolved. 
  &lt;span class=&#34;faded&#34;&gt;(18:21 UTC — Dec 21)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - All Singapore servers are back online at this time. We&amp;rsquo;ll continue to monitor. 
  &lt;span class=&#34;faded&#34;&gt;(17:31 UTC — Dec 21)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - Linode are investigating a connectivity issue in our Singapore data center. During this time, users may experience connection timeouts and errors for all services deployed in this data center. We will share additional updates as we have more information: &lt;a href=&#34;https://status.linode.com/incidents/wfghw8md5j8k&#34;&gt;https://status.linode.com/incidents/wfghw8md5j8k&lt;/a&gt; 
  &lt;span class=&#34;faded&#34;&gt;(16:52 UTC — Dec 21)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - Linode will be performing an emergency network maintenance to upgrade an aggregate switch pair in the AP-South (Singapore) data center on Monday, December 21, 2020 from 21:00 UTC until 23:00 UTC. While we do not expect any downtime during this maintenance there may be a period of brief packet loss or latency. (&lt;a href=&#34;https://status.linode.com/incidents/0cjzvsvxd8y2&#34;&gt;source&lt;/a&gt;) 
  &lt;span class=&#34;faded&#34;&gt;(04:02 UTC — Dec 21)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;Singapore VPS and NS may have experienced connectivity problems due to network connectivity issues in Linode&amp;rsquo;s Singapore data center: &lt;a href=&#34;https://status.linode.com/incidents/zv7xb4plgzfm&#34;&gt;https://status.linode.com/incidents/zv7xb4plgzfm&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Linode reports that the issue is now resolved. We&amp;rsquo;ve reached out to them to find out the cause of the recurring network problems in Singapore and the corrective action that they are taking to minimize future disruptions of service. 
  &lt;span class=&#34;faded&#34;&gt;(11:00 UTC — Dec 20)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Network outage in Singapore</title>
        <link>https://opalstackstatus.com/issues/2020-12-18-network-outage-in-singapore/</link>
        <pubDate>Fri, 18 Dec 2020 17:30:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2020-12-18-network-outage-in-singapore/</guid>
        <category>2020-12-18 21:17:48</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - Linode reports the incident is resolved as of  Dec 18, 2020 20:01 UTC. 
  &lt;span class=&#34;faded&#34;&gt;(21:17 UTC — Dec 18)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - All Singapore services are back online, we&amp;rsquo;ll continue to monitor while Linode wraps this up. 
  &lt;span class=&#34;faded&#34;&gt;(18:24 UTC — Dec 18)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - Linode has identified the cause of the outage and is implementing a fix, we&amp;rsquo;re seeing the Singapore servers coming back online at this time. 
  &lt;span class=&#34;faded&#34;&gt;(18:11 UTC — Dec 18)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - Linode reports the incident is resolved as of  Dec 18, 2020 20:01 UTC. 
  &lt;span class=&#34;faded&#34;&gt;(21:17 UTC — Dec 18)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - All Singapore services are back online, we&amp;rsquo;ll continue to monitor while Linode wraps this up. 
  &lt;span class=&#34;faded&#34;&gt;(18:24 UTC — Dec 18)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - Linode has identified the cause of the outage and is implementing a fix, we&amp;rsquo;re seeing the Singapore servers coming back online at this time. 
  &lt;span class=&#34;faded&#34;&gt;(18:11 UTC — Dec 18)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - If your domain is using our Singapore name servers then as an interim fix please switch your domain&amp;rsquo;s NS to one of our other regions: &lt;a href=&#34;https://help.opalstack.com/article/48/what-are-your-name-servers&#34;&gt;https://help.opalstack.com/article/48/what-are-your-name-servers&lt;/a&gt; 
  &lt;span class=&#34;faded&#34;&gt;(17:33 UTC — Dec 18)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;An outage in the Linode Singapore data center is affecting connectivity to some Singapore NS and VPS: &lt;a href=&#34;https://status.linode.com/incidents/k740qss44w58&#34;&gt;https://status.linode.com/incidents/k740qss44w58&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll update this post when we have more info. 
  &lt;span class=&#34;faded&#34;&gt;(17:30 UTC — Dec 18)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Singapore servers were offline</title>
        <link>https://opalstackstatus.com/issues/2020-12-16-singapore-servers-were-offline/</link>
        <pubDate>Wed, 16 Dec 2020 11:36:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2020-12-16-singapore-servers-were-offline/</guid>
        <category>2020-12-16 20:44:35</category>
        <description>&lt;p&gt;At 11:36 UTC on Dec 16, 2020 Linode reported a network connectivity issue in their Singapore datacenter: &lt;a href=&#34;https://status.linode.com/incidents/bt9z0b25417j&#34;&gt;https://status.linode.com/incidents/bt9z0b25417j&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Customer servers and NS in Singapore were affected by this issue and may have been inaccessible at that time. The NS issue may have also affected any domain that uses our Singapore NS.&lt;/p&gt;
&lt;p&gt;Service was restored after approximately 2 hours and has been up since that time. 
  &lt;span class=&#34;faded&#34;&gt;(11:36 UTC — Dec 16)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;At 11:36 UTC on Dec 16, 2020 Linode reported a network connectivity issue in their Singapore datacenter: &lt;a href=&#34;https://status.linode.com/incidents/bt9z0b25417j&#34;&gt;https://status.linode.com/incidents/bt9z0b25417j&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Customer servers and NS in Singapore were affected by this issue and may have been inaccessible at that time. The NS issue may have also affected any domain that uses our Singapore NS.&lt;/p&gt;
&lt;p&gt;Service was restored after approximately 2 hours and has been up since that time. 
  &lt;span class=&#34;faded&#34;&gt;(11:36 UTC — Dec 16)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
  </channel>
</rss>
