Partly network outage - status?

Customer Support Customer Only Discussion
1

In network-outages Tanmaya reported that one of the exit-routes is failing, and therefore some networks are not reachable.

I did a traceroute from two different networks, on network #1 I can reach jodohost servers, but on network #2 I cannot. Strange is that both networks route across exactly the same pnap/internap routers.
Question from me is that this more looks like a network-block (firewall issue) to me instead of a link/router failure…

Another question: when is this fixed? My customers cannot receive mail and most of the sites are down.

See pings/traceroutes below:

[SIZE=“1”][FONT=“Courier New”][FONT=“Fixedsys”]from network #1:
C:>ping win21.m****here.biz

Pinging win21.m****here.biz [64.187.106.2] with 32 bytes of data:

Reply from 64.187.106.2: bytes=32 time=103ms TTL=113
Reply from 64.187.106.2: bytes=32 time=103ms TTL=113
Reply from 64.187.106.2: bytes=32 time=103ms TTL=113
Reply from 64.187.106.2: bytes=32 time=103ms TTL=113

Ping statistics for 64.187.106.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 103ms, Maximum = 103ms, Average = 103ms

C:>tracert win21.mhere.biz
Tracing route to win21.mhere.biz [64.187.106.2]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms k035.sbp.ams2.nl.above.net [62.4.95.97]
2 1 ms <1 ms <1 ms ge-1-2-0.mpr1.ams1.nl.above.net [64.125.26.74]
3 <1 ms <1 ms <1 ms xe-0-0-0.er1.ams1.nl.above.net [64.125.26.81]
4 1 ms <1 ms <1 ms above-gblx-2.ams1.nl.above.net [64.125.12.158]
5 103 ms 103 ms 103 ms internap.tengigabitethernet2-2.ar1.mia2.gblx.net [64.212.16.166]
6 103 ms 103 ms 103 ms border5.pc1.bbnet1.mia003.pnap.net [69.25.0.13]
7 103 ms 103 ms 103 ms webhosting-15.border5.mia003.pnap.net [216.52.162.66]
8 103 ms 103 ms 103 ms ibgp.border3.nota.mia.webhosting.net [64.71.226.34]
9 104 ms 103 ms 103 ms 64.71.225.26
10 103 ms 103 ms 103 ms JILLCWIN21 [64.187.106.2]

Trace complete.

From network #2 (which cannot reach jodohost):
C:>ping win21.mhere.biz
Pingen naar win21.mhere.biz [64.187.106.2] met 32 byte gegevens:
Time-out bij opdracht.
Time-out bij opdracht.
Time-out bij opdracht.
Time-out bij opdracht.

Ping-statistieken voor 64.187.106.2:
Pakketten: verzonden = 4, ontvangen = 0, verloren = 4
(100% verlies).

C:>tracert win21.mhere.biz
Bezig met het traceren van de route naar win21.mhere.biz [64.187.106.2]
via maximaal 30 hops:
1 1 ms 1 ms <1 ms fritz.box [192.168.1.1]
2 20 ms 61 ms 47 ms lo0.ar16.ams3.network.solcon.net [212.45.35.205]
3 18 ms 18 ms 20 ms vlan502.crs1.ams1.network.solcon.net [212.45.45.1]
4 20 ms 20 ms 19 ms ge-2-3-0.104.ar1.AMS1.gblx.net [64.214.174.225]
5 116 ms 117 ms 116 ms INTERNAP.Tengigabitethernet2-2.ar1.MIA2.gblx.net [64.212.16.166]
6 117 ms 116 ms 117 ms border5.pc2.bbnet2.mia003.pnap.net [69.25.0.77]
7 117 ms 116 ms 116 ms webhosting-15.border5.mia003.pnap.net [216.52.162.66]
8 121 ms 121 ms 121 ms ibgp.border3.nota.mia.webhosting.net [64.71.226.34]
9 123 ms 125 ms 123 ms 64.71.225.26
10 * * * Time-out bij opdracht.
11 * * * Time-out bij opdracht.
12 * * * Time-out bij opdracht.[/FONT][/FONT][/SIZE]

2

It isn’t anything with firewall it is BGP routing taking a different path back then came in, and not going out to some places properly.

when? :frowning: I am not 100% sure, I sent some letter a bit ago giving permission to try something on our IPs.

3

Posted a number of times in public area as well.

4

Yes thanks. And I see it’s fixed now!
Took a while (6hrs+), but glad that it’s not longer than a day…

5

I am really thankful that clients these days have multiple means to see that we are not ‘lying’ when we say the majority is working.

I understand such is bad, and we worked on it non stop till fixed(forgoing sleep here, and have to go in 2 hours so won’t get any), but when not in our control directly having to deal with upstream carriers adds complexity.