TigerNode Status (@TigerStatus) profile picture

TigerNode Status

@TigerStatus

@TigerNode service status updates. To contact support: https://teapawt.net/t.co/3YTCc0TZHa

uptime.tigernode.com
Joined May 2017
  • Tweets34
  • Following0
  • Followers10
WH1-BHS is currently offline due to an attack. We're working to get the abusive customer suspended and machine back online.
1
1
WH1-BHS is back online. Abusive customer suspended. We will continue to monitor this situation.
1
Network connectivity to MC7 and MC8 in BHS is out due to a UPS failure for the rack those machines are in.
1
1
Resolved.
Since about 12:30am CST (6/7/2019) there has been some packet loss for some customers due to a fiber cut on one of our upstream providers' cable. As of now it looks like all traffic is rerouted so we're just seeing temporarily high latency for affected customers. (1/2)
1
(2/2) Techs are close to finishing repairs on the cut fiber. Latency will return down to normal once the line is reactivated.
Working on mitigating DDoS attack against our website.
1
Dallas WH1 has been up for about 2 hours now. Continuing to monitor.
Dallas WH1 is down. Data center is aware and investigating again. Please remember that if you're affected by this, you're eligible for compensation - just open a ticket.
Dallas WH1 was brought back online last night around 1am.
We're aware of WH1 in Dallas being down. Waiting on response and fix from datacenter.
1
PDU fixed. WH1 is back online.
WH1 in Dallas is down due to a PDU (power distribution unit) failure at the data center. Waiting on DC technicians to fix the issue.
WH1 in Dallas is back online.
WH1 in Dallas is down due to a switch failure at Psychz (datacenter). They are working on a fix.
1
WH1 nginx issue resolved.
Websites on WH1 in Dallas are currently unaccessible due to nginx breaking. Currently working on a fix.
WH1 has been stable for over an hour now. Provider has told us the network issue is resolved.
Our provider is aware of and investigating the WH1 outage in Dallas.
Affected services have been stable for over an hour now so we're considering this resolved.
1
Load more