10.0.0.1 IP address resolving when it shouldn't

[MRothaus]

This morning, I noticed that I was able to successfully ping and tracert to IP 10.0.0.1.  That is supposedly a non-routing IP address.  I VPN to a company that uses the 10.0.0.x for their internal LAN, but I was not connected to the VPN at the time.

Another co-worker working from his home office also has Verizon FIOS, and he too says the 10.0.0.1 address is resolving.  Here is my tracert:

>tracert 10.0.0.1

Tracing route to VPN-FCC [10.0.0.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router [192.168.249.1]
2 5 ms 4 ms 4 ms L100.PHLAPA-VFTTP-91.verizon-gni.net [98.114.133.1]
3 7 ms 7 ms 4 ms G0-6-2-5.PHLAPA-LCR-21.verizon-gni.net [130.81.131.136]
4 5 ms 17 ms 5 ms 130.81.199.18
5 25 ms 27 ms 26 ms 0.xe-4-0-2.XL3.CHI13.ALTER.NET [152.63.65.126]
6 27 ms 26 ms 27 ms 10.0.0.1

Trace complete.

Anybody else notice this?  I have restarted both my PC and my Actiontec router, but it made no difference.  I'm fairly certain this problem is upstream and it is Verizon that is messed up.

[smith6612]

I'm seeing it here as well from a Verizon Business DSL connection.

Tracing route to 10.0.0.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.254.254
2 29 ms 28 ms 29 ms 10.41.21.1
3 31 ms 31 ms 32 ms P0-0-0-3.BFLONY-LCR-21.verizon-gni.net [130.81.195.224]
4 108 ms 39 ms 86 ms xe-1-1-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.34]
5 71 ms 67 ms 67 ms 0.xe-1-0-8.XL3.CHI13.ALTER.NET [152.63.64.202]6 66 ms 68 ms 67 ms 10.0.0.1

Trace complete.

For some reason Verizon's network is announcing an address that should not be able to route over the Internet. Not good 😕

[gs0b]

I'm seeing it in the Philly area on FiOS.  It appears to go the exact same node.

Tracing route to 10.0.0.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     6 ms     6 ms     7 ms  L100.PHLAPA-VFTTP-84.verizon-gni.net [98.114.194.1]
  3    10 ms    11 ms     9 ms  G0-6-2-2.PHLAPA-LCR-21.verizon-gni.net [130.81.109.140]
  4    61 ms     9 ms    11 ms  130.81.199.18
  5    29 ms    32 ms    32 ms  0.xe-1-0-8.XL3.CHI13.ALTER.NET [152.63.64.202]
  6    33 ms    31 ms    31 ms  10.0.0.1

Trace complete.

Weird.

[prisaz]

Sent to POC for last connection on route to private IP. Whois lists multiple POCs for these IP in route. First attempt to verizon.com failed, so I tried the first POC in the list. We shall see where it goes. It is all in the Verizon routers. Who knows who is asigned that 152.63.65.185 IP address, or if it is one of their routers. I could hit it real hard to find out what it is. But I figure why bother, and leave it to VZB!

From:  
Sent:    Thursday, May 30, 2013 10:49 PM
To:    verizon.com'
Cc:   verizon.com'
Subject:    FW: Why is this IP routing to a private IP 10.0.0.1?



From:
Sent: Thursday, May 30, 2013 10:46 PM
To:verizon.com
Subject: Why is this IP routing to a private IP 10.0.0.1?

Why is this IP routing to a private IP 10.0.0.1?
152.63.65.185

C:\Windows\system32>tracert 10.0.0.1

Tracing route to 10.0.0.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  moat.localdomain [192.168.2.1]
  2     2 ms     2 ms     1 ms  L100.WASHDC-VFTTP-69.verizon-gni.net [x.x.x.x]
  3     4 ms     3 ms     3 ms  G0-9-3-5.WASHDC-LCR-22.verizon-gni.net [130.81.184.200]
  4     3 ms     2 ms     3 ms  ae0-0.RES-BB-RTR1.verizon-gni.net [130.81.209.114]
  5    28 ms    28 ms    28 ms  0.xe-1-0-8.XL4.CHI13.ALTER.NET [152.63.65.185]
  6    27 ms    28 ms    28 ms  10.0.0.1

Trace complete.

C:\Windows\system32>

This URL is your friend. The top right corner provides much information. if you enter what you want.

https://www.arin.net/whois_tou.html

NetRange	152.63.0.0 - 152.63.255.255
CIDR	152.63.0.0/16
Name	UUNET-BACKBONE
Handle	NET-152-63-0-0-1
Parent	NET152 (NET-152-0-0-0-0)
Net Type	Direct Allocation
Origin AS
Organization	MCI Communications Services, Inc. d/b/a Verizon Business (MCICS)
Registration Date	1991-08-19
Last Updated	2012-03-20
Comments	ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
RESTful Link	http://whois.arin.net/rest/net/NET-152-63-0-0-1

[prisaz]

Email Addresses omitted based on TOS. But a ticket was generated, based on the route I sent to the email.

FYI.

I am not a  Verizon business customer, but perhaps based on the fact a trouble ticket was issued, someone will look at it.

Dear Verizon Business Customer,

We have received your correspondence and forwarded it to the appropriate personnel for processing.

To help us provide you with the best possible service, please refer to trouble ticket number ############ in all email or phone correspondence regarding this matter.  For your convenience, we have included it in the Subject line of this message, and will do so in any future email correspondence.  If you should need assistance in the future on a different issue, please do not re-use this same ticket number.

If you are interested in managing your accounts online please visit our Verizon Business Customer Center website at https://customercenter.verizonbusiness.com/.

Thank you,

Verizon Business Technical Support

[MRothaus]

Looks like the problem is partially resolved. ping requests to 10.0.0.1 are no longer returning anything.

Tracert still getting out on first hop, but no further:

tracert 10.0.0.1

Tracing route to 10.0.0.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router [192.168.249.1]
2 5 ms 4 ms 5 ms L100.PHLAPA-VFTTP-91.verizon-gni.net [98.114.133.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * G0-6-2-5.PHLAPA-LCR-21.verizon-gni.net [130.81.131.136] reports: Destination net unreachable.

Trace complete.

[prisaz]

Yes, it looks like they are now aware of the issue and working on whatever the cause. I am right across the creek from them. 40 min drive, probably 15 minute flight.

It looks like the information I sent last night made it to someone. At least Verizon Business is blocking the route, and now Verizon Online must take the lead. It does look like the issue is being worked, The buck now stops at Verizon Online. The business end must have seen it and said, what the....

Oh well, funny that it was spotted al all. That used to show as my PPPoE default gateway. I suspect changes are in the works for something. I am DHCP since changing my service.

C:\Windows\system32>tracert 10.0.0.1

Tracing route to 10.0.0.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  moat.localdomain [x.x.x.x]
  2     2 ms     1 ms     1 ms  L100.WASHDC-VFTTP-69.verizon-gni.net [x.x.x.x]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *     G0-9-2-5.WASHDC-LCR-22.verizon-gni.net [130.81.105.164]  reports: Destination net unreachable.

Trace complete.

C:\Windows\system32>

NetRange	130.81.0.0 - 130.81.255.255
CIDR	130.81.0.0/16
Name	VZGNI-PUB-7
Handle	NET-130-81-0-0-1
Parent	NET130 (NET-130-0-0-0-0)
Net Type	Direct Allocation
Origin AS
Organization	Verizon Online LLC (VRIS)
Registration Date	1988-06-29
Last Updated	2012-03-02
Comments	ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
RESTful Link	http://whois.arin.net/rest/net/NET-130-81-0-0-1
See Also	Related organization's POC records.
See Also	Related delegations.

[MRothaus]

Been a while, but 10.0.0.1 is resolving again here (PA FIOS, residential):

>tracert 10.0.0.1

Tracing route to 10.0.0.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router [192.168.249.1]
2 3 ms 4 ms 4 ms L100.PHLAPA-VFTTP-91.verizon-gni.net [98.114.133.1]
3 10 ms 12 ms 12 ms G0-6-2-5.PHLAPA-LCR-21.verizon-gni.net [130.81.131.136]
4 17 ms 12 ms 12 ms ae0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.209.178]
5 11 ms 12 ms 12 ms ge-7-0-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.19.63]
6 * * * Request timed out.
7 * * * Request timed out.
8 55 ms 56 ms 117 ms 0.ae2.XT3.DFW9.ALTER.NET [140.222.225.55]
9 72 ms 57 ms 55 ms 10.0.0.1

Trace complete.

Looks similar to what happened in May 2013.  Anybody else confirming this?

[Hubrisnxs · Accepted solution]

10.x.x.x are sometimes VZ Dslams for DSL customers, and also serve as PPPoE concentrator private IP's for PPPoE customers

All FAQs → Verizon Online DSL FAQ → 3. General

What is the 10.4.3.1 IP?

you guys might be in DSL or PPPoE area's

[josepne3]

On a 10.0.0.1 ip address, a virtual NAT server may be installed. Modem You can change DSL or PPPoE field settings.