bgpreport

Network · data from 2026-11-12

AS57660 Com4

Registry name: COM4-AS Com4 AS, NO · PeeringDB

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

Announced routes

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

193.27.94.0/23 No ROA Other origin only 670 100% 67
37.26.208.0/20 No ROA RIR databaseRIPE 672 100% 67
212.67.48.0/20 No ROA RIR databaseRIPE 672 100% 67
185.67.16.0/22 No ROA RIR databaseRIPE 670 100% 67
185.242.144.0/22 No ROA RIR databaseRIPE 670 100% 67
2a00:67c0::/32 No ROA RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS57660: AS-COM4. 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 (AS57660 isn't in the set, or no route object for AS57660 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 objectsAS57660 in itNot covered
AS-COM4 RIPE 217 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 7 are in fix.csv.

  • ROA: none6
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none193.27.94.0/23No ROA covers it. Add a ROA for AS57660, maxLength 23.670 of 673
Route object: none193.27.94.0/23Route objects for it name AS31096. Add a route object with origin AS57660 in the RIR database for the space.670 of 673
ROA: none37.26.208.0/20No ROA covers it. Add a ROA for AS57660, maxLength 20.672 of 673
ROA: none212.67.48.0/20No ROA covers it. Add a ROA for AS57660, maxLength 20.672 of 673
ROA: none185.67.16.0/22No ROA covers it. Add a ROA for AS57660, maxLength 22.670 of 673
ROA: none185.242.144.0/22No ROA covers it. Add a ROA for AS57660, maxLength 22.670 of 673
ROA: none2a00:67c0::/32No ROA covers it. Add a ROA for AS57660, maxLength 32.635 of 636

Route objects not announced

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