bgpreport

Network · data from 2026-11-12

AS22847 BOWDOIN

Registry name: BOWDOIN - Bowdoin College, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22847, 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.
66.63.115.0/24 Invalid: origin Other origin only 54 8%low visibility 35
216.195.188.0/22 Invalid: origin Other origin only 53 8%low visibility 33
139.140.0.0/16 Valid Other IRR onlyALTDB, RADB 670 100% 69
139.140.0.0/17 Valid Other IRR onlyRADB 670 100% 69
139.140.128.0/17 Valid Other IRR onlyRADB 670 100% 69
2620:0:2b79::/48 Valid Other IRR onlyALTDB, RADB 635 100% 70
2620:0:2b70::/44 Valid Other IRR onlyALTDB, RADB 634 100% 70
2620:0:2b7a::/48 Valid Other IRR onlyRADB 634 100% 70

AS-SET

AS22847's PeeringDB record names no AS-SET.

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

  • ROA: origin2
  • Route object: none2
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin66.63.115.0/24ROAs covering it name AS5760, not AS22847. If AS22847 should announce it, add a ROA for AS22847.54 of 673
Route object: none66.63.115.0/24Route objects for it name AS5760. Add a route object with origin AS22847 in the RIR database for the space.54 of 673
ROA: origin216.195.188.0/22ROAs covering it name AS5760, not AS22847. If AS22847 should announce it, add a ROA for AS22847.53 of 673
Route object: none216.195.188.0/22Route objects for it name AS5760. Add a route object with origin AS22847 in the RIR database for the space.53 of 673
Route object: RIR139.140.0.0/16Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR139.140.0.0/17Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR139.140.128.0/17Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2620:0:2b79::/48Route object only in ALTDB, RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2620:0:2b70::/44Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2620:0:2b7a::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

2602:fd40::/36RADBValid
2620:0:2b70::/48RADBValid

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.