bgpreport

Network · data from 2026-11-12

AS22557 IDENTITYDIGITAL - Identity Digital Inc.

Registry name: IDENTITYDIGITAL - Identity Digital Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22557, 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.
69.64.144.0/24 No ROA Other IRR onlyRADB 673 100% 67
69.64.145.0/24 No ROA Other IRR onlyRADB 673 100% 67
69.64.158.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

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

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
ROA: none69.64.144.0/24No ROA covers it. Add a ROA for AS22557, maxLength 24.673 of 673
Route object: RIR69.64.144.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none69.64.145.0/24No ROA covers it. Add a ROA for AS22557, maxLength 24.673 of 673
Route object: RIR69.64.145.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none69.64.158.0/24No ROA covers it. Add a ROA for AS22557, maxLength 24.673 of 673
Route object: RIR69.64.158.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

69.64.144.0/20RADBNo ROA
69.64.146.0/23RADBNo ROA
69.64.146.0/24ARINInvalid: origin
69.64.148.0/23RADBNo ROA
69.64.155.0/24ARINInvalid: origin
69.64.156.0/24ARINInvalid: origin
69.64.157.0/24RADBNo ROA
69.64.159.0/24RADBNo ROA
104.244.184.0/22RADBNo ROA
104.244.184.0/24RADBNo ROA
104.244.185.0/24RADBNo ROA
104.244.186.0/24RADBNo ROA
198.147.208.0/22RADBNo ROA
198.147.208.0/24ARINInvalid: origin
198.147.209.0/24ARIN, RADBNo ROA
198.147.210.0/23RADBNo ROA
198.147.210.0/24ARINInvalid: origin
198.147.211.0/24ARIN, RADBNo ROA
2620:115:3000::/44RADBNo ROA
2620:115:3000::/48RADBNo ROA
2620:115:3001::/48RADBNo ROA
2620:115:3002::/48RADBNo 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.