Are we discussing direct connectivity between 15169/174?
or via a third party(ies)? I ask, because i looks like RouteViews has, in:
http://archive.routeviews.org/bgpdata/2020.07/UPDATES/updates.20200715.0345.bz2
at last this bit of clues:
BGP4MP_ET|1594784883.404691|A|91.218.184.60|49788|35.213.0
On 6/8/22 15:41, David Hubbard wrote:
Appears HE (ASN6939) is still
unreachable though… I feel like less entities are single homed to HE,
but it would still be a calculated risk.
HE is the 800-pound gorilla of IPv6. I would be leery of a carrier
without reachability to AS6939.
--
Jay Henni
I've had zero issues reaching Google via Cogent, however Google didn't pick
up transit from Cogent themselves: They got transit from Tata, which makes
them reachable via Cogent due to the peering relationship between Cogent
and Tata.
Regards,
Peter
On Wed, Jun 8, 2022 at 6:45 PM David Hubbard
wr
It seemed like a decade in the making but has the IPv6 transit between Cogent
and Google (via that showed up last fall remained stable? I’d ruled them out
on a number of projects for this reason but may reconsider if it has been
reliable. Appears HE (ASN6939) is still unreachable though… I fe
4 matches
Mail list logo
