bgpreport

Network · data from 2026-11-12

AS36083 IPDEPLOY

Registry name: IPDEPLOY - IPDeploy, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36083, 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.138.8.0/24 No ROA None 672 100% 67
2602:fb51::/48 No ROA None 634 100% 67
2602:fb51:1::/48 No ROA None 634 100% 67
38.141.37.0/24 No ROA Other IRR onlyRADB 669 99% 68
38.143.62.0/24 No ROA Other IRR onlyRADB 669 99% 68
23.156.72.0/24 No ROA RIR databaseARIN 669 99% 68
2602:fa73::/48 No ROA RIR databaseARIN 634 100% 69
2602:fa73:1::/48 No ROA RIR databaseARIN 634 100% 69
2602:fa73:2::/48 No ROA RIR databaseARIN 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS36083: AS-IPDEPLOY. 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 (AS36083 isn't in the set, or no route object for AS36083 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 objectsAS36083 in itNot covered
AS-IPDEPLOY In no IRR database read today.

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

  • ROA: none9
  • Route object: none3
  • Route object: RIR2
  • AS-SET: not found1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none23.138.8.0/24No ROA covers it. Add a ROA for AS36083, maxLength 24.672 of 673
Route object: none23.138.8.0/24No route object for it. Add a route object with origin AS36083 in the RIR database for the space.672 of 673
ROA: none2602:fb51::/48No ROA covers it. Add a ROA for AS36083, maxLength 48.634 of 636
Route object: none2602:fb51::/48No route object for it. Add a route object with origin AS36083 in the RIR database for the space.634 of 636
ROA: none2602:fb51:1::/48No ROA covers it. Add a ROA for AS36083, maxLength 48.634 of 636
Route object: none2602:fb51:1::/48No route object for it. Add a route object with origin AS36083 in the RIR database for the space.634 of 636
ROA: none38.141.37.0/24No ROA covers it. Add a ROA for AS36083, maxLength 24.669 of 673
Route object: RIR38.141.37.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none38.143.62.0/24No ROA covers it. Add a ROA for AS36083, maxLength 24.669 of 673
Route object: RIR38.143.62.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none23.156.72.0/24No ROA covers it. Add a ROA for AS36083, maxLength 24.669 of 673
ROA: none2602:fa73::/48No ROA covers it. Add a ROA for AS36083, maxLength 48.634 of 636
ROA: none2602:fa73:1::/48No ROA covers it. Add a ROA for AS36083, maxLength 48.634 of 636
ROA: none2602:fa73:2::/48No ROA covers it. Add a ROA for AS36083, maxLength 48.634 of 636
AS-SET: not foundAS-IPDEPLOYPeeringDB names AS-IPDEPLOY; no IRR database read has it.

Route objects not announced

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

72.5.153.0/24RADBNo 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.