Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Is burst.net down?
Is burst.net down?
| Posted by thomas81, 12-22-2011, 11:59 AM |
I cannot able to access this web site, also my vps.
Can anyone here help me check? |
| Posted by Patrick, 12-22-2011, 12:03 PM |
Quote:
|
Originally Posted by thomas81
I cannot able to access this web site, also my vps.
Can anyone here help me check?
|
Works from here. Post a traceroute! |
| Posted by thomas81, 12-22-2011, 12:12 PM |
I using ISP from www.singnet.com.sg no problem, but ISP www.starhub.com got problem.
C:\Users\user>tracert www.thomas81.com
Tracing route to www.thomas81.com [96.9.149.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 15 ms 13 ms 14 ms bb116-15-54-1.singnet.com.sg [116.15.54.1]
3 14 ms 14 ms 14 ms xe-11-2-0-3414.sherry.singnet.com.sg [202.166.12
1.9]
4 14 ms 14 ms 13 ms te3-0-1-3434.sake.singnet.com.sg [202.166.119.49
]
5 16 ms 14 ms 13 ms xe-2-2-0-0.budweiser.singnet.com.sg [202.166.126
.9]
6 15 ms 15 ms 15 ms ae1-0.beck.singnet.com.sg [202.166.124.234]
7 16 ms 16 ms 15 ms 203.208.190.130
8 15 ms 19 ms 15 ms ge-1-1-9-0.sngc3-dr1.ix.singtel.com [203.208.182
.133]
9 190 ms 263 ms 191 ms 203.208.171.186
10 198 ms 258 ms 210 ms 203.208.171.154
11 186 ms 203 ms 193 ms paix-sj.1-2.r1.sj.hwng.net [198.32.176.76]
12 195 ms 221 ms 195 ms 1-2.r1.la.hwng.net [209.197.1.146]
13 243 ms 273 ms 302 ms e3-4.r1.ch.hwng.net [209.197.0.26]
14 307 ms 314 ms 322 ms unknown.hwng.net [209.197.0.38]
15 269 ms 286 ms 293 ms 2-3.r1.ny.hwng.net [69.16.191.93]
16 285 ms 272 ms 298 ms 209.197.17.130
17 288 ms 286 ms 305 ms 209.197.17.134
18 295 ms 294 ms 271 ms xe1-03.agg04.sctn01.hostnoc.net [64.120.243.38]
19 297 ms 272 ms 293 ms ec0-61.bf2803.sctn01.hostnoc.net [96.9.184.61]
20 289 ms 269 ms 273 ms vserver13.hostnoc.net [66.96.241.10]
21 279 ms 282 ms 279 ms 96-9-149-99.static.hostnoc.net [96.9.149.99]
Trace complete.
C:\Users\user>tracert www.thomas81.com
Unable to resolve target system name www.thomas81.com.
C:\Users\user>tracert www.thomas81.com
Unable to resolve target system name www.thomas81.com.
C:\Users\user>tracert 96.9.149.99
Tracing route to 96.9.149.99 over a maximum of 30 hops
1 9 ms 14 ms 7 ms cm1.kappa132.maxonline.com.sg [58.182.132.1]
2 16 ms 29 ms 7 ms 172.20.42.1
3 9 ms 6 ms 7 ms 172.26.42.1
4 8 ms 8 ms 48 ms 172.20.7.2
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 ^C
C:\Users\user>tracert burst.net
Unable to resolve target system name burst.net.
C:\Users\user>tracert www.burst.net
Tracing route to root.burst.net [66.96.192.202]
over a maximum of 30 hops:
1 17 ms 7 ms 8 ms cm1.kappa132.maxonline.com.sg [58.182.132.1]
2 9 ms 7 ms 7 ms 172.20.42.1
3 10 ms 7 ms 12 ms 172.26.42.1
4 10 ms 7 ms 7 ms 172.20.7.2
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 ^C
C:\Users\user> |
| Posted by JaJae, 12-22-2011, 12:18 PM |
|
It never gets out of the private IP network. Check your ISP or DNS. |
| Posted by Matt R, 12-22-2011, 12:19 PM |
Sounds like an issue on your side of things. Your first traceroute shows you successfully reaching your own server. The others suggest that your computer isn't properly resolving DNS, until you get to the one for burst.net which shows that your ISP is having issues as the traceroute fails long before it even leaves your ISP's network.
I'd call your ISP, not Burst. |
| Posted by rustelekom, 12-22-2011, 03:11 PM |
Hi all,
Why not just do check by just-ping.com? Or by host-tracker.com. It is most easy way to check are there really issue happen or you need touch to your ISP and ask them to solve problem ASAP. |
Add to Favourites 
Print this Article
Also Read
Shared Hosting
Shared Hosting
