bgpreport

Network · data from 2026-11-12

AS398712 ISPCONNECTED

Registry name: ISPCONNECTED - ISPCONNECTED CORP, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS398712, 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.
23.226.28.0/22 No ROA Nonecovered by 23.226.16.0/20 673 100% 67
190.111.160.0/22 Valid Other IRR onlyALTDB 669 99% 67
2605:f540::/32 Valid Other IRR onlyALTDB 635 100% 69
52.128.8.0/22 Valid RIR databaseALTDB, ARIN 673 100% 67
52.128.12.0/22 Valid RIR databaseALTDB, ARIN 673 100% 67
94.131.68.0/22 Valid RIR databaseRIPE 673 100% 67
23.165.240.0/24 Valid RIR databaseALTDB, ARIN 670 100% 67
23.227.72.0/22 Valid RIR databaseARIN 670 100% 67
23.227.76.0/22 Valid RIR databaseARIN 670 100% 67
23.227.80.0/22 Valid RIR databaseARIN 670 100% 67
23.227.88.0/22 Valid RIR databaseARIN 670 100% 67
45.4.196.0/22 Valid RIR databaseALTDB, ARIN 670 100% 67
52.128.0.0/22 Valid RIR databaseALTDB, ARIN 670 100% 67
52.128.4.0/22 Valid RIR databaseALTDB, ARIN 670 100% 67
2803:c880::/32 Valid RIR databaseALTDB, LACNIC 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS398712: AS-ISPCON. 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 (AS398712 isn't in the set, or no route object for AS398712 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 objectsAS398712 in itNot covered
AS-ISPCON RIPE 1119 Yes 0
ARIN (also) 2120 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 9 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none23.226.28.0/22No ROA covers it. Add a ROA for AS398712, maxLength 22.673 of 673
Route object: none23.226.28.0/22No route object for it. A route object for 23.226.16.0/20 with origin AS398712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398712 in the RIR database for the space.673 of 673
Route object: RIR190.111.160.0/22Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR2605:f540::/32Route object only in ALTDB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

23.226.16.0/20ALTDBNo ROA
23.227.64.0/22ARINInvalid: origin
52.128.0.0/20ALTDBNo ROA
2001:470:584::/48ARINValid
2803:3ec0::/48ALTDBNo 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.