Author Topic: Master Server Down  (Read 2935 times)

I am happy there is a post clearing things up.

Yeah, thanks for clearing everything up, badspot.


:o is happeningall over again.

But why is Blockbot spamming on rtb?

But why is Blockbot spamming on rtb?
To get it through some people thick skulls

Thanks for clarifying this. I'll just build in single player.

Yeah since the server went down everyone went into chaos and i was about to say on IRC "/me Says: Spah Sappin' Mah Blockland" but before i even got finished typing it Block Bot banned me off of RTB for no reason!

Warning - while you were typing a new reply has been posted. You may wish to review your post.
Shut up

Edit: If Block Bot ever lifts my ban, and yes ever I might live happily ever after. xD
« Last Edit: August 04, 2009, 09:10:45 PM by SpyCrab »

Ephi banned alot of people.  And kicked.

I heard it's up again...


Yup, it surely was down.

Here are the results of pinging them.

Code: [Select]
# ping master.blockland.us
PING master.blockland.us (70.86.174.34): 56 data bytes
64 bytes from 70.86.174.34: icmp_seq=2508 ttl=114 time=3546.390 ms
64 bytes from 70.86.174.34: icmp_seq=2509 ttl=114 time=2546.662 ms
64 bytes from 70.86.174.34: icmp_seq=2510 ttl=114 time=1547.020 ms
64 bytes from 70.86.174.34: icmp_seq=2511 ttl=114 time=547.405 ms
64 bytes from 70.86.174.34: icmp_seq=2512 ttl=114 time=3567.810 ms
64 bytes from 70.86.174.34: icmp_seq=2513 ttl=114 time=2516.058 ms
64 bytes from 70.86.174.34: icmp_seq=2514 ttl=114 time=1516.385 ms
64 bytes from 70.86.174.34: icmp_seq=2515 ttl=114 time=517.051 ms
64 bytes from 70.86.174.34: icmp_seq=2516 ttl=114 time=3554.551 ms
64 bytes from 70.86.174.34: icmp_seq=2517 ttl=114 time=2551.933 ms
64 bytes from 70.86.174.34: icmp_seq=2518 ttl=114 time=1550.327 ms
64 bytes from 70.86.174.34: icmp_seq=2519 ttl=114 time=550.665 ms
64 bytes from 70.86.174.34: icmp_seq=2520 ttl=114 time=3562.617 ms
64 bytes from 70.86.174.34: icmp_seq=2521 ttl=114 time=2557.833 ms
- ÜberSnip -
Code: [Select]
64 bytes from 70.86.174.34: icmp_seq=2733 ttl=114 time=3537.436 ms
64 bytes from 70.86.174.34: icmp_seq=2734 ttl=114 time=2537.486 ms
64 bytes from 70.86.174.34: icmp_seq=2735 ttl=114 time=1537.872 ms
64 bytes from 70.86.174.34: icmp_seq=2736 ttl=114 time=538.155 ms
64 bytes from 70.86.174.34: icmp_seq=2737 ttl=114 time=3547.841 ms
64 bytes from 70.86.174.34: icmp_seq=2738 ttl=114 time=2544.987 ms
64 bytes from 70.86.174.34: icmp_seq=2739 ttl=114 time=1545.634 ms
64 bytes from 70.86.174.34: icmp_seq=2740 ttl=114 time=545.742 ms
64 bytes from 70.86.174.34: icmp_seq=2741 ttl=114 time=3555.340 ms
64 bytes from 70.86.174.34: icmp_seq=2742 ttl=114 time=2554.247 ms
64 bytes from 70.86.174.34: icmp_seq=2743 ttl=114 time=1554.648 ms
64 bytes from 70.86.174.34: icmp_seq=2744 ttl=114 time=555.499 ms
64 bytes from 70.86.174.34: icmp_seq=2745 ttl=114 time=3545.556 ms
64 bytes from 70.86.174.34: icmp_seq=2746 ttl=114 time=2545.559 ms
64 bytes from 70.86.174.34: icmp_seq=2747 ttl=114 time=1543.598 ms
64 bytes from 70.86.174.34: icmp_seq=2748 ttl=114 time=543.649 ms
ping: sendto: Network is down
ping: sendto: Network is down
ping: sendto: No route to host
ping: sendto: No route to host
64 bytes from 70.86.174.34: icmp_seq=2756 ttl=114 time=3785.011 ms
64 bytes from 70.86.174.34: icmp_seq=2758 ttl=114 time=1785.737 ms
64 bytes from 70.86.174.34: icmp_seq=2759 ttl=114 time=785.389 ms
64 bytes from 70.86.174.34: icmp_seq=2760 ttl=114 time=3772.130 ms
64 bytes from 70.86.174.34: icmp_seq=2761 ttl=114 time=2772.707 ms
64 bytes from 70.86.174.34: icmp_seq=2762 ttl=114 time=1772.728 ms
64 bytes from 70.86.174.34: icmp_seq=2763 ttl=114 time=771.067 ms
64 bytes from 70.86.174.34: icmp_seq=2764 ttl=114 time=3756.017 ms
64 bytes from 70.86.174.34: icmp_seq=2765 ttl=114 time=2756.590 ms
64 bytes from 70.86.174.34: icmp_seq=2766 ttl=114 time=1756.682 ms
64 bytes from 70.86.174.34: icmp_seq=2767 ttl=114 time=756.883 ms
64 bytes from 70.86.174.34: icmp_seq=2768 ttl=114 time=3763.219 ms
64 bytes from 70.86.174.34: icmp_seq=2769 ttl=114 time=2763.343 ms
64 bytes from 70.86.174.34: icmp_seq=2770 ttl=114 time=1762.946 ms
64 bytes from 70.86.174.34: icmp_seq=2771 ttl=114 time=762.224 ms
64 bytes from 70.86.174.34: icmp_seq=2772 ttl=114 time=3778.255 ms
64 bytes from 70.86.174.34: icmp_seq=2773 ttl=114 time=2778.534 ms
64 bytes from 70.86.174.34: icmp_seq=2774 ttl=114 time=1779.251 ms
64 bytes from 70.86.174.34: icmp_seq=2775 ttl=114 time=779.173 ms
64 bytes from 70.86.174.34: icmp_seq=2776 ttl=114 time=3769.081 ms
64 bytes from 70.86.174.34: icmp_seq=2777 ttl=114 time=2767.885 ms
64 bytes from 70.86.174.34: icmp_seq=2778 ttl=114 time=1767.521 ms
64 bytes from 70.86.174.34: icmp_seq=2779 ttl=114 time=767.439 ms
64 bytes from 70.86.174.34: icmp_seq=2780 ttl=114 time=3789.956 ms
64 bytes from 70.86.174.34: icmp_seq=2781 ttl=114 time=2789.675 ms
64 bytes from 70.86.174.34: icmp_seq=2782 ttl=114 time=1790.038 ms
64 bytes from 70.86.174.34: icmp_seq=2783 ttl=114 time=790.406 ms
^C
--- master.blockland.us ping statistics ---
2788 packets transmitted, 268 packets received, 90% packet loss
round-trip min/avg/max/stddev = 116.865/2106.368/5293.318/1181.754 ms

That's a horrible response time by the way.
« Last Edit: August 04, 2009, 07:07:57 PM by BobAndRob »

eiter sprites or fnding out how to animate my avatar

Thanks for the confirmation that it was down, "BobAndRob", we were a bit unsure.

So it was due to a packet loss?