bgpreport

Network · data from 2026-11-12

AS10578 Northern Crossroads

Registry name: GIGAPOP-NE - Harvard University, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10578, 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.
18.2.192.0/19 No ROA None 2 0%low visibility 2
2603:40ff:6000::/36 No ROA None 1 0%low visibility 1
2001:504:2e::/48 No ROA Other IRR onlyRADB 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS10578: AS10578:AS-ALL. 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 (AS10578 isn't in the set, or no route object for AS10578 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 objectsAS10578 in itNot covered
AS10578:AS-ALL RADB1 member set in no database: AS10578:AS-HPS 1915148 Yes 2

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 9 are in fix.csv.

  • ROA: none3
  • Route object: none2
  • Route object: RIR1
  • AS-SET: missing member1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none18.2.192.0/19No ROA covers it. Add a ROA for AS10578, maxLength 19.2 of 673
Route object: none18.2.192.0/19No route object for it. Add a route object with origin AS10578 in the RIR database for the space.2 of 673
ROA: none2603:40ff:6000::/36No ROA covers it. Add a ROA for AS10578, maxLength 36.1 of 636
Route object: none2603:40ff:6000::/36No route object for it. Add a route object with origin AS10578 in the RIR database for the space.1 of 636
ROA: none2001:504:2e::/48No ROA covers it. Add a ROA for AS10578, maxLength 48.1 of 636
Route object: RIR2001:504:2e::/48Route object only in RADB. Add it in the RIR database for the space.1 of 636
AS-SET: missing memberAS10578:AS-ALLAS10578:AS-ALL (RADB) lists AS10578:AS-HPS; no IRR database read has it.

Route objects not announced

Route objects with origin AS10578 whose prefix no peer sees AS10578 announce. Many are kept on purpose (backup routes, space announced only in some places).

192.5.89.0/24ARIN, RADBValid
2001:468:600::/40ARINNo ROA

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.