Re: Facebook IP Geolocation

2023-04-28 Thread Peter Potvin via NANOG 
Hey there TJ,

I have, and unfortunately the databases listed there are reporting the
location correctly. It seems to be an issue specifically with Facebook from
what I'm able to diagnose. I've been reached out to by someone from their
network team regarding this so will update this thread when/if it gets
resolved.

Regards,
Peter Potvin | Executive Director
--
*Accuris Technologies Ltd.*
56A Mill St E, Unit #470, Acton, ON L7J 1H3 Canada
Email: peter.pot...@accuristechnologies.ca
Office: +1 (877) 352-6105
Network Operations Center: +1 (877) 321-1662


On Fri, Apr 28, 2023 at 6:21 AM TJ Trout  wrote:

> Have you checked these?
>
> https://thebrotherswisp.com/index.php/geo-and-vpn/
>
> On Fri, Apr 28, 2023, 1:58 AM Peter Potvin via NANOG 
> wrote:
>
>> Hey all,
>>
>> Recently a customer reached out to us regarding an IP of ours in Canada
>> that Facebook is somehow placing within China, despite our geolocation in
>> other databases showing up correctly as they're ingesting our geofeeds as
>> we had requested.
>>
>> Does anyone know which geolocation databases Facebook uses, and if
>> possible a contact at Meta we can reach out to so that this can be
>> investigated further?
>>
>> Thanks in advance!
>>
>> Regards,
>> Peter Potvin | Executive Director
>>
>> --
>> *Accuris Technologies Ltd.*
>>
>

Re: BGP Books

2023-04-28 Thread Jeff Tantsura 
If you are looking for BGP in DC (either unicast and/or VPN) we (Jeff Doyle and I) have published a significant number of podcasts on “between 0x2 nerds”(from basic BGP to EVPN to BGP security to HW) - https://youtube.com/playlist?list=PLMYH1xDLIabuZCr1Yeoo39enogPA2yJB7Cheers,JeffOn Apr 27, 2023, at 15:37, Warren Kumari  wrote:On Tue, Apr 25, 2023 at 7:20 PM, Steven G. Huter  wrote:On 4/25/23 3:55 PM, Lyndon Nerenberg (VE7TFX/VE6BBM) wrote: It has been a couple of decades since I've done any BGP in anger,
but it looks like I will be jumping into the deep end again, soon,
and I desperately need to get up to speed again. There seem to be a lot of good guides out there from Cisco, Juniper,
and the like, but naturally they are very product oriented.  What
I'm looking for is more like the Stevens networking bibles (i.e.  "BGP Illustrated Vol I and II"). Something that covers more than
just the raw protocols, and includes things like RPKI.  (The world
sure has changed since the last time I was doing this!)Any/all suggestions welcome. https://learn.nsrc.org/bgpYes, this. Much of it (all of it?) is presented by Philip Smith, and he's a sufficiently entertaining speaker that it's worth watching even if you are already a bgp "expert". As for books — I used to buy a copy of "BGP4: Inter-Domain Routing in the Internet" by John W Stewart for all of my new hires — https://amzn.to/3VdqdfK . It's really short and sweet, and covers just the stuff that you need to know. It is old at this point (1998!), but still well worth the read.WSteve

Weekly Global IPv4 Routing Table Report

2023-04-28 Thread Routing Table Analysis Role Account 
This is an automated weekly mailing describing the state of the Global
IPv4 Routing Table as seen from APNIC's router in Japan.

The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG
TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG.

Daily listings are sent to bgp-st...@lists.apnic.net.

For historical data, please see https://thyme.apnic.net.

If you have any comments please contact Philip Smith .

IPv4 Routing Table Report   04:00 +10GMT Sat 29 Apr, 2023

  BGP Table (Global) as seen in Japan.

Report Website: https://thyme.apnic.net
Detailed Analysis:  https://thyme.apnic.net/current/

Analysis Summary


BGP routing table entries examined:  920274
Prefixes after maximum aggregation (per Origin AS):  349049
Deaggregation factor:  2.64
Unique aggregates announced (without unneeded subnets):  449049
Total ASes present in the Internet Routing Table: 74365
Prefixes per ASN: 12.38
Origin-only ASes present in the Internet Routing Table:   63787
Origin ASes announcing only one prefix:   26221
Transit ASes present in the Internet Routing Table:   10578
Transit-only ASes present in the Internet Routing Table:435
Average AS path length visible in the Internet Routing Table:   4.3
Max AS path length visible:  55
Max AS path prepend of ASN (265020)  50
Prefixes from unregistered ASNs in the Routing Table:  1078
Number of instances of unregistered ASNs:  1078
Number of 32-bit ASNs allocated by the RIRs:  41758
Number of 32-bit ASNs visible in the Routing Table:   34510
Prefixes from 32-bit ASNs in the Routing Table:  170749
Number of bogon 32-bit ASNs visible in the Routing Table:13
Special use prefixes present in the Routing Table:1
Prefixes being announced from unallocated address space:635
Number of addresses announced to Internet:   3060323968
Equivalent to 182 /8s, 104 /16s and 214 /24s
Percentage of available address space announced:   82.7
Percentage of allocated address space announced:   82.7
Percentage of available address space allocated:  100.0
Percentage of address space in use by end-sites:   99.6
Total number of prefixes smaller than registry allocations:  307168

APNIC Region Analysis Summary
-

Prefixes being announced by APNIC Region ASes:   243681
Total APNIC prefixes after maximum aggregation:   69357
APNIC Deaggregation factor:3.51
Prefixes being announced from the APNIC address blocks:  237917
Unique aggregates announced from the APNIC address blocks:97908
APNIC Region origin ASes present in the Internet Routing Table:   13396
APNIC Prefixes per ASN:   17.76
APNIC Region origin ASes announcing only one prefix:   3929
APNIC Region transit ASes present in the Internet Routing Table:   1802
Average APNIC Region AS path length visible:4.5
Max APNIC Region AS path length visible: 26
Number of APNIC region 32-bit ASNs visible in the Routing Table:   8699
Number of APNIC addresses announced to Internet:  773438208
Equivalent to 46 /8s, 25 /16s and 187 /24s
APNIC AS Blocks4608-4864, 7467-7722, 9216-10239, 17408-18431
(pre-ERX allocations)  23552-24575, 37888-38911, 45056-46079, 55296-56319,
   58368-59391, 63488-64098, 64297-64395, 131072-151865
APNIC Address Blocks 1/8,  14/8,  27/8,  36/8,  39/8,  42/8,  43/8,
49/8,  58/8,  59/8,  60/8,  61/8, 101/8, 103/8,
   106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8,
   116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8,
   123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8,
   163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8,
   203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8,
   222/8, 223/8,

ARIN Region Analysis Summary


Prefixes being announced by ARIN Region ASes:269219
Total ARIN prefixes after maximum aggregation:   122319
ARIN Deaggregation factor: 2.20
Prefixes being announced from the ARIN address blocks:   271854
Unique aggregates announced from the ARIN address blocks:131001
ARIN Region origin ASes present in the Internet Routing Table:19089
ARIN Prefixes per ASN:

Re: Spectrum networks IPv6 access issue

2023-04-28 Thread Sam Thomas 
Actual data from a Spectrum residential customer in DFW.

First, IPv4:

 trace dfw.source.kernel.org
traceroute to dfw.source.kernel.org (139.178.84.217), 64 hops max, 40
byte packets
 1  my.router  0.389 ms  0.350 ms  0.292 ms
 2  142-254-130-077.inf.spectrum.com (142.254.130.77)  8.423 ms  8.408
ms  8.080 ms
 3  lag-63.artrtx2801h.netops.charter.com (24.28.88.17)  27.167 ms
25.065 ms  21.977 ms
 4  lag-22.artntxaf01r.netops.charter.com (24.175.49.233)  10.718 ms
10.083 ms  15.886 ms
 5  lag-23.mcr11crtntxjt.netops.charter.com (24.175.36.224)  13.386 ms
 11.560 ms  11.297 ms
 6  lag-21.rcr01dllatx37.netops.charter.com (24.175.49.0)  11.339 ms
lag-28.rcr01dllatx37.netops.charter.com (24.175.33.246)  11.904 ms
 128.186 ms
 7  lag-414.dllstx976iw-bcr00.netops.charter.com (66.109.6.52)  12.603 ms
lag-14.dllstx976iw-bcr00.netops.charter.com (66.109.6.88)  12.172 ms
lag-414.dllstx976iw-bcr00.netops.charter.com (66.109.6.52)  12.299 ms
 8  lag-302.pr3.dfw10.netops.charter.com (209.18.43.77)  21.570 ms
lag-0.pr3.dfw10.netops.charter.com (66.109.5.121)  11.763 ms
lag-302.pr3.dfw10.netops.charter.com (209.18.43.77)  12.182 ms
 9  dls-b23-link.ip.twelve99.net (62.115.156.208)  11.515 ms *  11.706 ms
10  packethost-ic-369414.ip.twelve99-cust.net (213.248.72.3)  11.870
ms  30.246 ms  18.199 ms
11  * * *
12  * * *
13  dfw.source.kernel.org (139.178.84.217)  12.021 ms  12.076 ms  11.922 ms

ping dfw.source.kernel.org
PING dfw.source.kernel.org (139.178.84.217): 56 data bytes
64 bytes from 139.178.84.217: icmp_seq=0 ttl=50 time=11.590 ms
64 bytes from 139.178.84.217: icmp_seq=1 ttl=50 time=11.785 ms

IPv6:

 trace6 dfw.source.kernel.org
traceroute6 to dfw.source.kernel.org (2604:1380:4641:c500::1) from
2603:8080:REDACTED, 64 hops max, 20 byte packets
 1  2603-8080-REDACTED.res6.spectrum.com  0.404 ms  0.340 ms  0.322 ms
 2  2603-90c5-0003-000e----0001.inf6.spectrum.com  10.308
ms  7.901 ms  9.902 ms
 3  lag-63.artrtx2801h.netops.charter.com  17.008 ms  10.523 ms  11.077 ms
 4  lag-22.artntxaf01r.netops.charter.com  14.638 ms * *
 5  lag-23.mcr11crtntxjt.netops.charter.com  11.090 ms  11.612 ms  12.234 ms
 6  * * *
 7  lag-414.dllstx976iw-bcr00.netops.charter.com  12.572 ms *
lag-24.dllstx976iw-bcr00.netops.charter.com  12.160 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  *^C

ping6 dfw.source.kernel.org
PING6(56=40+8+8 bytes) 2603:8080:REDACTED --> 2604:1380:4641:c500::1
^C
--- dfw.source.kernel.org ping6 statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss

I have a Linode VM in Dallas that I also can't get to via IPv6.
Traffic appears to take the same path for IPv4.

On Wed, Apr 26, 2023 at 10:50 AM Tom Rini  wrote:
>
> Hey all,
>
> I'm posting this here in hopes of getting the attention of someone that
> can get this issue resolved, or at least an internal ticket filed. I've
> tried the customer-facing tech support and not been able to get such a
> thing done.
>
> In short, from within Spectrum's US IPv6 network (verified in both North
> Carolina and Ohio), dfw.source.kernel.org (2604:1380:4641:c500::1) is
> unreachable and connections time out. This site is otherwise fine and
> globally accessible via IPv6, tested on both Qwest and T-Mobile hosted
> systems.  This is a regression from some time in early April this year.
>
> --
> Tom

Re: Facebook IP Geolocation

2023-04-28 Thread TJ Trout 
Have you checked these?

https://thebrotherswisp.com/index.php/geo-and-vpn/

On Fri, Apr 28, 2023, 1:58 AM Peter Potvin via NANOG 
wrote:

> Hey all,
>
> Recently a customer reached out to us regarding an IP of ours in Canada
> that Facebook is somehow placing within China, despite our geolocation in
> other databases showing up correctly as they're ingesting our geofeeds as
> we had requested.
>
> Does anyone know which geolocation databases Facebook uses, and if
> possible a contact at Meta we can reach out to so that this can be
> investigated further?
>
> Thanks in advance!
>
> Regards,
> Peter Potvin | Executive Director
>
> --
> *Accuris Technologies Ltd.*
>

Facebook IP Geolocation

2023-04-28 Thread Peter Potvin via NANOG 
Hey all,

Recently a customer reached out to us regarding an IP of ours in Canada
that Facebook is somehow placing within China, despite our geolocation in
other databases showing up correctly as they're ingesting our geofeeds as
we had requested.

Does anyone know which geolocation databases Facebook uses, and if possible
a contact at Meta we can reach out to so that this can be investigated
further?

Thanks in advance!

Regards,
Peter Potvin | Executive Director
--
*Accuris Technologies Ltd.*