Dear team
We are suffering issue from our upstream for US Region prefix
--
Mitesh Patel
Oparation Head | Dishawaves Infonet Pvt. Ltd.
Cell - 94266 55866 |HelpDesk – 99042 56666
302, Matrix, Near Divyabhaskar Press, Corporate Road, Prahalad nagar, Ahmedabad – 380015
Please consider the environment before printing this e-mail.
Dear Anurag,
Our Noida customers are also reported same issue & as you mentioned, all the impacted Vodafone prefixes are learning from outside India.
We are still not received complaints from our Mumbai customers so suspecting that Vodafone have changed routing of specific location routes (North India) only.
We are coordinating with our upstream providers to get update from Vodafone Team.
Regards,
Mahesh Palaye
From: Raj Sharma [mailto:raj@mnetconnect.com]
Sent: 13 August 2020 23:33
To: INNOG Public Mailing list; Anurag Bhatia
Cc: tech
Subject: [INNOG] Re: Vodafone AS55410 routing issues today?
Hi Anurag
Have asked my Downstream AS58590 who also has AS55410 as his upstream Peer to check with Vodafone on his direct tickets raised to Vodafone
I will update the same here once I get updates
Thanks and regards,
Raj Sharma,
Assistant General Manager - Technical Head
M-Net Fiber Fast
AS132960
Sent from my iPhone
13.08.2020, 23:26, "Anurag Bhatia" <me@anuragbhatia.com>:
OK - Some more details. My good friend Doug Madory notied drop of Tata Comm AS6453 transit by Vodafone (twitter discussion here).
So I traced one of Vodafone India IP - 42.106.11.1 via all Indian RIPE Atlas probes and found this:
Jio -> Vodafone is from outside of India:
Traceroute to 42.106.11.1 (42.106.11.1), 48 byte packets
1 * * *
2 210.18.186.1 AS17488 1.816ms 1.615ms 1.838ms
3 202.88.152.245 AS17488 2.208ms 2.689ms 2.869ms
4 136.232.29.73 136.232.29.73.static.jio.com AS55836 3.51ms 2.667ms 2.74ms
5 103.198.140.62 AS64049 3.935ms 3.721ms 3.475ms
6 103.198.140.17 AS64049 36.524ms 36.58ms 36.976ms
7 103.198.140.17 AS64049 35.96ms 35.753ms 36.206ms
8 62.115.177.10 snge-b1-link.telia.net AS1299 38.486ms 466.176ms 66.607ms
9 80.239.130.210 cablewireless-ic-318568-sng-b2.c.telia.net AS1299 40.977ms 37.501ms 37.921ms
10 195.2.24.166 ae2-xcr2.sgs.cw.net AS1273 36.734ms 36.752ms 37.745ms
11 195.89.108.214 AS1273 90.377ms 87.643ms 87.61ms
12 182.19.105.121 AS55410 123.017ms * 123.815ms
13 100.64.0.126 118.055ms 118.74ms 117.496ms
14 * * *
15 * * *
Downstream of Sify > Sify > Vodafone is also from outside of India:
Traceroute to 42.106.11.1 (42.106.11.1), 48 byte packets
1 192.168.0.1 0.595ms 0.52ms 0.446ms
2 1.0.24.10 2.275ms 3.288ms 2.186ms
3 45.116.1.45 45-116-1-45.rev.expl.in AS134053 2.134ms 2.044ms 2.239ms
4 1.7.151.4 AS132215 31.111ms 30.115ms 29.543ms
5 1.7.150.102 AS9583 29.827ms 30.194ms 32.622ms
6 100.65.231.150 120.064ms 120.152ms 118.596ms
7 100.65.231.150 117.115ms 119.975ms 121.212ms
8 63.217.24.133 te0-2-0-20.br03.sin02.pccwbtn.net AS3491 116.155ms 118.149ms 105.401ms
9 63.218.165.62 63-218-165-62.static.pccwglobal.net AS3491 181.275ms 181.288ms 181.726ms
10 195.2.24.166 ae2-xcr2.sgs.cw.net AS1273 191.441ms 191.216ms 191.154ms
11 195.89.108.214 AS1273 124.734ms 143.46ms 124.93ms
12 182.19.105.121 AS55410 127.83ms 127.935ms 127.15ms
13 100.64.0.126 120.859ms 121.013ms 120.807ms
14 * * *
15 * * *
ACT -> Vodafone is also from outside of India:
BSNL -> Vodafone India is also from outside of India:
Traceroute to 42.106.11.1 (42.106.11.1), 48 byte packets
1 192.168.1.1 1.404ms 0.817ms 0.752ms
2 117.242.108.1 AS9829 6.854ms 7.066ms 6.711ms
3 218.248.173.65 AS9829 6.201ms 7.051ms 6.765ms
4 218.248.107.82 static.ill.218.248.107.82/24.bsnl.in AS9829 7.002ms 6.865ms 6.776ms
5 117.216.207.202 AS9829 14.443ms 14.44ms 14.385ms
6 117.216.207.203 AS9829 14.581ms 14.563ms 14.451ms
7 115.110.78.173 AS4755 20.492ms 21.025ms 21.002ms
8 172.23.183.134 AS9498 42.32ms 41.959ms 42.096ms
9 180.87.38.5 ix-ae-0-100.tcore1.mlv-mumbai.as6453.net AS6453 135.491ms 135.111ms 135.816ms
10 180.87.38.2 if-ae-2-2.tcore2.mlv-mumbai.as6453.net AS6453 160.395ms 161.125ms 160.575ms
11 180.87.39.21 if-ae-12-2.tcore1.l78-london.as6453.net AS6453 162.728ms 162.862ms *
12 80.231.130.130 if-ae-17-2.tcore1.ldn-london.as6453.net AS6453 165.299ms 165.141ms 165.059ms
13 195.219.83.211 AS6453 209.081ms 204.502ms 209.749ms
14 * * *
15 223.196.24.18 366.111ms * 362.12ms
16 223.196.1.217 AS55644 186.795ms 187.232ms *
17 * * *
18 * * *
I also checked NIXI route servers to see if Vodafone AS55410 routes are visible and saw quite low number of routes from AS55410. Strange case.
Airtel seems to be dropping traffic as well as per RIPE Atlas traces.
from their looking glass saw:
AS path: 174 9583 55644 55410 38266 ? (Originator)
AS path: 3491 1273 55410 38266 I (Originator)
So Vodafone India lost connectivity to virtually all networks in India inside India and routing from outside of India. Unsure why.
Anyone got any replies from Vodafone on direct tickets?
Hi Apoorv and Anurag,
My Downstream peer AS58590 also reported issues as he has AS55410 as his upstream
They had faced issues on some routes and applications
Guys ,Any specific subnets which got impacted .
Thanks and regards,
Raj Sharma,
Assistant General Manager - Technical Head
M-Net Fiber Fast
AS132960
Sent from my iPhone
10:39 pm, 13 August 2020, Anurag Bhatia <me@anuragbhatia.com>:
I heard both Tata Comm and Vodafone were missing many of their routes besides NIXI route server. Though I cannot verify that. I checked routes of Vodafone AS55410 announced outside of India mostly behind Vodafone/C&W AS1273 and those announcements seem consistent.
Wondering if the issues you faced were with domestic Indian connectivity only?
Hi
Vodafone is our upstream..and we are facing issue.
Hi Anurag
One of my downstream peers who also has Vodafone also as his upstream peer has faced issues this evening on some routes and certain applications were not working
Asst.General Manager-Technical Head
Sent from my iPhone
Anyone heard about Vodafone AS55410 routing issues today? I hear many key backbones were missing their routes. Anyone else also facing this issue?
_______________________________________________
INNOG mailing list -- innog@innog.net
To unsubscribe send an email to innog-leave@innog.net
_______________________________________________
INNOG mailing list -- innog@innog.net
To unsubscribe send an email to innog-leave@innog.net
--
--
