Is it down - Re-boot.jpg 64.72KB
0 downloads
Chris Cosgrove
Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.
Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.
reboot.pro down
Started by
BeigeBochs
, Jun 27 2024 07:18 PM
18 replies to this topic
#16
Chris Cosgrove
-
- Global Moderator
- 28,257 posts
- OFFLINE
- Gender:Male
- Location:Scotland
- Local time:04:32 AM
Posted Today, 05:57 PM
Back to top
#17
BeigeBochs
- Topic Starter
-
- Members
- 271 posts
- ONLINE
- Local time:08:32 PM
Posted Today, 06:55 PM
Yes, yes, but why!? Is it a temporary outage for maintenance or upgrade? Internet service outage? Server crash? Billing issue? Office politics? Takedown notice?
#18
cryptodan
-
- Members
- 35,210 posts
- OFFLINE
Bleepin Madman
- Gender:Male
- Location:USA
- Local time:03:32 AM
Posted Today, 07:02 PM
US Navy Veteran from 2002 to 2006
Masters in Computer and Digital Forensics Expert - Stevenson University Alumni 2015
Arch Desktop - https://termbin.com/epij
Arch Laptop - https://www.termbin.com/dnwk
Ubuntu Server - https://termbin.com/zvra
#19
BeigeBochs
- Topic Starter
-
- Members
- 271 posts
- ONLINE
- Local time:08:32 PM
Posted Today, 08:13 PM
That topic dates back to April. And it ends with reboot.pro coming back online a couple days later.
But the situation may be repeating.
Like "roytam1", I also ran a traceroute for reboot.pro, and it ended similarly with:
18 189 ms 183 ms 197 ms core21.fsn1.hetzner.com [213.239.254.221]
19 189 ms 181 ms 183 ms blocked.hetzner.com [88.198.255.174]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 blocked.hetzner.com [88.198.255.174] reports: Destination net unreachable.
But the situation may be repeating.
Like "roytam1", I also ran a traceroute for reboot.pro, and it ended similarly with:
18 189 ms 183 ms 197 ms core21.fsn1.hetzner.com [213.239.254.221]
19 189 ms 181 ms 183 ms blocked.hetzner.com [88.198.255.174]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 blocked.hetzner.com [88.198.255.174] reports: Destination net unreachable.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
