bgpreport

Network · data from 2026-11-12

AS36481 DIGITALEDGE-VENTURES-INC - DIGITAL EDGE VENTURES INC.

Registry name: DIGITALEDGE-VENTURES-INC - DIGITAL EDGE VENTURES INC., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36481, 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.
208.74.200.0/24 No ROA Other origin onlycovered by 208.74.200.0/22 671 100% 67
208.74.201.0/24 No ROA Other origin onlycovered by 208.74.200.0/22 671 100% 67
208.74.202.0/24 No ROA Other origin onlycovered by 208.74.200.0/22 671 100% 67
208.74.203.0/24 No ROA Other origin onlycovered by 208.74.200.0/22 671 100% 67
208.74.200.0/22 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS36481 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: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none208.74.200.0/24No ROA covers it. Add a ROA for AS36481, maxLength 24.671 of 673
Route object: none208.74.200.0/24Route objects for it name AS29791. A route object for 208.74.200.0/22 with origin AS36481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36481 in the RIR database for the space.671 of 673
ROA: none208.74.201.0/24No ROA covers it. Add a ROA for AS36481, maxLength 24.671 of 673
Route object: none208.74.201.0/24Route objects for it name AS29791. A route object for 208.74.200.0/22 with origin AS36481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36481 in the RIR database for the space.671 of 673
ROA: none208.74.202.0/24No ROA covers it. Add a ROA for AS36481, maxLength 24.671 of 673
Route object: none208.74.202.0/24Route objects for it name AS29791. A route object for 208.74.200.0/22 with origin AS36481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36481 in the RIR database for the space.671 of 673
ROA: none208.74.203.0/24No ROA covers it. Add a ROA for AS36481, maxLength 24.671 of 673
Route object: none208.74.203.0/24Route objects for it name AS29791. A route object for 208.74.200.0/22 with origin AS36481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36481 in the RIR database for the space.671 of 673
ROA: none208.74.200.0/22No ROA covers it. Add a ROA for AS36481, maxLength 22.673 of 673
Route object: RIR208.74.200.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

162.218.140.0/22RADBNo ROA
2607:c800::/32ALTDBNo 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.