bgpreport

Network · data from 2026-11-12

AS21750 Counterpoint Networking

Registry name: CPOINT-NET-1 - CPOINT, US · PeeringDB

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

Announced routes

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

204.10.49.0/24 No ROA RIR databaseALTDB, ARIN 673 100% 68
204.10.51.0/24 No ROA RIR databaseALTDB, ARIN 673 100% 68
204.10.48.0/22 No ROA RIR databaseARIN 672 100% 67
204.10.48.0/23 No ROA RIR databaseALTDB, ARIN 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS21750: AS-CPOINT. 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 (AS21750 isn't in the set, or no route object for AS21750 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 objectsAS21750 in itNot covered
AS-CPOINT RIPE 1110 Yes 0
ALTDB (also) 1110 Yes 0
ARIN (also) 1110 Yes 0

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

  • ROA: none4
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none204.10.49.0/24No ROA covers it. Add a ROA for AS21750, maxLength 24.673 of 673
ROA: none204.10.51.0/24No ROA covers it. Add a ROA for AS21750, maxLength 24.673 of 673
ROA: none204.10.48.0/22No ROA covers it. Add a ROA for AS21750, maxLength 22.672 of 673
ROA: none204.10.48.0/23No ROA covers it. Add a ROA for AS21750, maxLength 23.672 of 673

Route objects not announced

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

204.10.50.0/23ALTDB, ARINNo ROA
207.202.116.0/23ARINInvalid: origin
207.202.116.0/24ARINInvalid: origin
207.202.117.0/24ARINInvalid: origin
2602:ffee:50::/44RADBNo ROA
2602:ffee:fa0::/44RADBNo 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.