bgpreport

Network · data from 2026-11-12

AS13506 US-DEPARTMENT-OF-THE-TREASURY - United States Department of the Treasury

Registry name: US-DEPARTMENT-OF-THE-TREASURY - United States Department of the Treasury, US · not in PeeringDB

10IPv4 routes 60.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
8Route objects not announced registered with origin AS13506, seen from no peer

Announced routes

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

199.169.192.0/24 No ROA RIR databaseARIN 673 100% 67
199.169.193.0/24 No ROA RIR databaseARIN 673 100% 67
199.169.197.0/24 No ROA RIR databaseARIN 673 100% 67
199.169.199.0/24 No ROA RIR databaseARIN 673 100% 67
164.95.95.0/24 Valid RIR databaseARIN 673 100% 67
164.95.204.0/24 Valid RIR databaseARIN 673 100% 67
166.123.204.0/24 Valid RIR databaseARIN 673 100% 67
166.123.208.0/24 Valid RIR databaseARIN 673 100% 67
164.95.0.0/16 Valid RIR databaseARIN, RADB 672 100% 67
166.123.0.0/16 Valid RIR databaseARIN, RADB 672 100% 67
2610:108:3100::/40 Valid RIR databaseARIN 634 100% 68
2610:108:4100::/40 Valid RIR databaseARIN 632 99% 68

AS-SET

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

  • ROA: none4
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none199.169.192.0/24No ROA covers it. Add a ROA for AS13506, maxLength 24.673 of 673
ROA: none199.169.193.0/24No ROA covers it. Add a ROA for AS13506, maxLength 24.673 of 673
ROA: none199.169.197.0/24No ROA covers it. Add a ROA for AS13506, maxLength 24.673 of 673
ROA: none199.169.199.0/24No ROA covers it. Add a ROA for AS13506, maxLength 24.673 of 673

Route objects not announced

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

199.169.194.0/24ARINNo ROA
199.169.195.0/24ARINNo ROA
2610:108::/32ARINValid
2610:108::/33ARINValid
2610:108:3000::/48ALTDBInvalid: maxLength
2610:108:4000::/48ALTDBInvalid: maxLength
2610:108:8000::/34ARINValid
2610:108:bf10::/44ARINValid

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.