Anyone from Peloton Interactive on the list?

2019-03-29 Thread Mike Lyon
If so, please contact me off list.

Thank You,
Mike


-- 
Mike Lyon
mike.l...@gmail.com
http://www.linkedin.com/in/mlyon


Contact wanted: abc.go.com

2019-03-29 Thread Eddie Parra
Does anyone have a contact for abc.go.com?  If so, could you please contact me 
offline?  

Thanks,

-Eddie

Qwest CenturyLink / Telia issues near Seattle?

2019-03-29 Thread Aaron C. de Bruyn via NANOG
For the past ~36 hours I have been seeing 15% packet loss between
CenturyLink and Telia.

I regularly access equipment in a Wave Broadband datacenter in Longview, WA
from my office connected via ToldeoTel and the traffic transits
Qwest/CenturyLink over to Telia before hitting Wave.

I have a handful of clients affected too.

I contacted Wave yesterday and they said CenturyLink is aware that the link
to Telia is 'completely saturated' and working on it.  I contacted Wave
again today to see if they had an update and they said no.  ToledoTel
didn't have any update either.

Can anyone shed some light on it?  Or an ETA for resolving it?

Thanks,

-A


Weekly Routing Table Report

2019-03-29 Thread Routing Analysis Role Account
This is an automated weekly mailing describing the state of the Internet
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 http://thyme.rand.apnic.net.

If you have any comments please contact Philip Smith .

Routing Table Report   04:00 +10GMT Sat 30 Mar, 2019

Report Website: http://thyme.rand.apnic.net
Detailed Analysis:  http://thyme.rand.apnic.net/current/

Analysis Summary


BGP routing table entries examined:  742948
Prefixes after maximum aggregation (per Origin AS):  285249
Deaggregation factor:  2.60
Unique aggregates announced (without unneeded subnets):  358190
Total ASes present in the Internet Routing Table: 63769
Prefixes per ASN: 11.65
Origin-only ASes present in the Internet Routing Table:   54888
Origin ASes announcing only one prefix:   23710
Transit ASes present in the Internet Routing Table:8881
Transit-only ASes present in the Internet Routing Table:269
Average AS path length visible in the Internet Routing Table:   4.4
Max AS path length visible:  34
Max AS path prepend of ASN ( 25081)  32
Prefixes from unregistered ASNs in the Routing Table:29
Number of instances of unregistered ASNs:32
Number of 32-bit ASNs allocated by the RIRs:  26387
Number of 32-bit ASNs visible in the Routing Table:   21522
Prefixes from 32-bit ASNs in the Routing Table:   94294
Number of bogon 32-bit ASNs visible in the Routing Table:28
Special use prefixes present in the Routing Table:0
Prefixes being announced from unallocated address space:267
Number of addresses announced to Internet:   2845039488
Equivalent to 169 /8s, 147 /16s and 219 /24s
Percentage of available address space announced:   76.8
Percentage of allocated address space announced:   76.8
Percentage of available address space allocated:  100.0
Percentage of address space in use by end-sites:   99.2
Total number of prefixes smaller than registry allocations:  248634

APNIC Region Analysis Summary
-

Prefixes being announced by APNIC Region ASes:   200727
Total APNIC prefixes after maximum aggregation:   57903
APNIC Deaggregation factor:3.47
Prefixes being announced from the APNIC address blocks:  197663
Unique aggregates announced from the APNIC address blocks:82276
APNIC Region origin ASes present in the Internet Routing Table:9640
APNIC Prefixes per ASN:   20.50
APNIC Region origin ASes announcing only one prefix:   2717
APNIC Region transit ASes present in the Internet Routing Table:   1422
Average APNIC Region AS path length visible:4.5
Max APNIC Region AS path length visible: 30
Number of APNIC region 32-bit ASNs visible in the Routing Table:   4617
Number of APNIC addresses announced to Internet:  769678720
Equivalent to 45 /8s, 224 /16s and 93 /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-139577
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:219503
Total ARIN prefixes after maximum aggregation:   103821
ARIN Deaggregation factor: 2.11
Prefixes being announced from the ARIN address blocks:   218452
Unique aggregates announced from the ARIN address blocks:104995
ARIN Region origin ASes present in the Internet Routing Table:18421
ARIN Prefixes per ASN:11.86
ARIN 

Re: Was wrong Re: Did IPv6 between HE and Google ever get resolved?

2019-03-29 Thread Job Snijders
A careful observer will note multiple fractures/rifts in the ipv6
default-free zone. It’s not as meshed as ipv4, unfortunately.

Kind regards,

Job


RE: Was wrong Re: Did IPv6 between HE and Google ever get resolved?

2019-03-29 Thread Jon Lewis

On Fri, 29 Mar 2019, Aaron Gould wrote:


Why does cogent seem like the commonality between those 2 that you mentioned  :|


Why do people think the policy as to whether or not they can peer or have 
to buy transit should be different for one address family vs the other?


Why will some networks peer at an IX but refuse to make changes (like new 
port IPs or new ASN for the same organization they already peer with)?


Regardless, this is why it pays to multi-home and peer as much as 
possible.  If you directly peer with the networks one of your transit 
providers is in a pissing match with, the issue is easily ignored.


--
 Jon Lewis, MCP :)   |  I route
 |  therefore you are
_ http://www.lewis.org/~jlewis/pgp for PGP public key_


RE: Was wrong Re: Did IPv6 between HE and Google ever get resolved?

2019-03-29 Thread Aaron Gould
Why does cogent seem like the commonality between those 2 that you mentioned  :|

- Aaron

-
"I think what you were remembering is Cogent/Google and Cogent/HE are both 
IPv6 issues where the parties can't agree on peering vs transit for the v6 
relationship."