bgpreport

Network · data from 2026-11-12

AS33199 ASN-AMHERSTCOMM-01 - Amherst Communications

Registry name: ASN-AMHERSTCOMM-01 - Amherst Communications, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS33199, 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.
2603:b018::/32 Invalid: origin None 31 5%low visibility 21
135.132.192.0/18 No ROA None 669 99% 67
167.253.132.0/22 Valid RIR databaseARIN 670 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin2603:b018::/32ROAs covering it name AS11796, not AS33199. If AS33199 should announce it, add a ROA for AS33199.31 of 636
Route object: none2603:b018::/32No route object for it. Add a route object with origin AS33199 in the RIR database for the space.31 of 636
ROA: none135.132.192.0/18No ROA covers it. Add a ROA for AS33199, maxLength 18.669 of 673
Route object: none135.132.192.0/18No route object for it. Add a route object with origin AS33199 in the RIR database for the space.669 of 673

Route objects not announced

Every route object with origin AS33199 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.