We have a status page to check our service, and found out the frontend hosted on netlify was down.
The status check is done by sending a request to tidbcloud.com, and the request at the time is below:
HEAD https://tidbcloud.com
{
"User-Agent": "Mozilla/5.0+(compatible; UptimeRobot/2.0; http://www.uptimerobot.com/)",
"Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8",
"Accept-Language": "en-US,en;q=0.8",
"Connection": "close",
"cache-control": "no-cache",
"Referer": "https://tidbcloud.com",
"Accept-encoding": ""
}
And this is trace route result:
traceroute
Tracing route to 104.198.14.52
hop no - node ip - ms
1 → 216.245.209.213(2 ms)
2 → 63.143.63.129(5478 ms)
3 → 104.198.14.52(14999 ms) Request timed out
4 → 104.198.14.52(15000 ms) Request timed out
5 → 206.53.202.109(7 ms)
6 → 104.198.14.52(44 ms)
dns is like below:
❯ dig tidbcloud.com
; <<>> DiG 9.10.6 <<>> tidbcloud.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26786
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 5
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;tidbcloud.com. IN A
;; ANSWER SECTION:
tidbcloud.com. 600 IN A 104.198.14.52
;; AUTHORITY SECTION:
tidbcloud.com. 448 IN NS ns45.domaincontrol.com.
tidbcloud.com. 448 IN NS ns46.domaincontrol.com.
;; ADDITIONAL SECTION:
ns46.domaincontrol.com. 263 IN A 173.201.70.23
ns45.domaincontrol.com. 440 IN A 97.74.102.23
ns46.domaincontrol.com. 367 IN AAAA 2603:5:2262::17
ns45.domaincontrol.com. 502 IN AAAA 2603:5:2162::17
;; Query time: 170 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Sat Dec 23 13:49:02 CST 2023
;; MSG SIZE rcvd: 198
We are currently investigating this incident and hope we can get some help from here.