bgpreport

Network · data from 2026-11-12

AS13359 LEARN Caching and Peering

Registry name: LEARN-CACHING-PEERING - LEARN, US · PeeringDB

2IPv4 routes 0.0% RPKI valid · 50.0% with a route object
2IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS13359, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS13359, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
74.200.186.0/24 No ROA Other origin only 63 9%low visibility 33
2607:f928:4::/48 No ROA Other IRR onlyRADB 345 54% 65
2607:f928:16::/48 No ROA Other IRR onlyRADB 244 38% 60
74.200.189.0/24 No ROA Other IRR onlyRADB 201 30% 56

AS-SET

PeeringDB's irr_as_set for AS13359: RADB::AS-LEARN-INST. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS13359 isn't in the set, or no route object for AS13359 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS13359 in itNot covered
RADB::AS-LEARN-INST RADB 1143907 Yes 1

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 8 are in fix.csv.

  • ROA: none4
  • Route object: none1
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none74.200.186.0/24No ROA covers it. Add a ROA for AS13359, maxLength 24.63 of 673
Route object: none74.200.186.0/24Route objects for it name AS16905. Add a route object with origin AS13359 in the RIR database for the space.63 of 673
ROA: none2607:f928:4::/48No ROA covers it. Add a ROA for AS13359, maxLength 48.345 of 636
Route object: RIR2607:f928:4::/48Route object only in RADB. Add it in the RIR database for the space.345 of 636
ROA: none2607:f928:16::/48No ROA covers it. Add a ROA for AS13359, maxLength 48.244 of 636
Route object: RIR2607:f928:16::/48Route object only in RADB. Add it in the RIR database for the space.244 of 636
ROA: none74.200.189.0/24No ROA covers it. Add a ROA for AS13359, maxLength 24.201 of 673
Route object: RIR74.200.189.0/24Route object only in RADB. Add it in the RIR database for the space.201 of 673

Route objects not announced

Every route object with origin AS13359 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.