bgpreport

Network · data from 2026-11-12

AS11681 INTEGRITY - Integrity Networks

Registry name: INTEGRITY - Integrity Networks, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11681, 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.
172.93.112.0/21 No ROA RIR databaseARIN 671 100% 67
204.14.160.0/21 No ROA RIR databaseALTDB, ARIN, RADB 671 100% 67
209.218.130.0/23 Valid RIR databaseALTDB, ARIN 669 99% 67
209.218.208.0/22 Valid RIR databaseALTDB, ARIN 669 99% 67

AS-SET

AS11681 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: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none172.93.112.0/21No ROA covers it. Add a ROA for AS11681, maxLength 21.671 of 673
ROA: none204.14.160.0/21No ROA covers it. Add a ROA for AS11681, maxLength 21.671 of 673

Route objects not announced

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

204.14.160.0/22ALTDBNo ROA
204.14.164.0/22ALTDBNo 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.