bgpreport

Network · data from 2026-11-12

AS18463 MILLPOND-NET-01 - Mill Pond Networks LLC

Registry name: MILLPOND-NET-01 - Mill Pond Networks LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18463, 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.

38.49.192.0/20 No ROA None 673 100% 67
38.61.32.0/20 No ROA None 673 100% 67
2604:21e0:4030::/44 No ROA Nonecovered by 2604:21e0::/32 635 100% 67
2604:21e0:7020::/44 No ROA Nonecovered by 2604:21e0::/32 605 95% 67
38.60.0.0/18 Valid RIR databaseARIN 673 100% 67

AS-SET

AS18463 isn't in PeeringDB, where networks name their 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 9 are in fix.csv.

  • ROA: none4
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.49.192.0/20No ROA covers it. Add a ROA for AS18463, maxLength 20.673 of 673
Route object: none38.49.192.0/20No route object for it. Add a route object with origin AS18463 in the RIR database for the space.673 of 673
ROA: none38.61.32.0/20No ROA covers it. Add a ROA for AS18463, maxLength 20.673 of 673
Route object: none38.61.32.0/20No route object for it. Add a route object with origin AS18463 in the RIR database for the space.673 of 673
ROA: none2604:21e0:4030::/44No ROA covers it. Add a ROA for AS18463, maxLength 44.635 of 636
Route object: none2604:21e0:4030::/44No route object for it. A route object for 2604:21e0::/32 with origin AS18463 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18463 in the RIR database for the space.635 of 636
ROA: none2604:21e0:7020::/44No ROA covers it. Add a ROA for AS18463, maxLength 44.605 of 636
Route object: none2604:21e0:7020::/44No route object for it. A route object for 2604:21e0::/32 with origin AS18463 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18463 in the RIR database for the space.605 of 636

Route objects not announced

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

2604:21e0::/32ARINNo 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.