bgpreport

Network · data from 2026-11-12

AS393256 DTE-ASN - DTE Energy Company

Registry name: DTE-ASN - DTE Energy Company, US · not in PeeringDB

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

Announced routes

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

162.9.64.0/18 No ROA Nonecovered by 162.9.0.0/16 673 100% 67
162.9.140.0/24 No ROA Nonecovered by 162.9.0.0/16 673 100% 67
162.9.0.0/17 No ROA Nonecovered by 162.9.0.0/16 670 100% 68
162.9.0.0/18 No ROA Nonecovered by 162.9.0.0/16 670 100% 68
162.9.140.0/23 No ROA Nonecovered by 162.9.0.0/16 670 100% 68
162.9.141.0/24 No ROA Nonecovered by 162.9.0.0/16 670 100% 68
2606:fec0:1::/48 Valid Nonecovered by 2606:fec0::/32 636 100% 68
2606:fec0:8000::/48 Valid Nonecovered by 2606:fec0::/32 636 100% 68
2606:fec0::/47 Valid Nonecovered by 2606:fec0::/32 635 100% 70
2606:fec0::/48 Valid Nonecovered by 2606:fec0::/32 635 100% 70
2606:fec0:8000::/47 Valid Nonecovered by 2606:fec0::/32 635 100% 70
204.124.152.0/22 Valid Other IRR onlyRADB 670 100% 68

AS-SET

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

  • ROA: none6
  • Route object: none11
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none162.9.64.0/18No ROA covers it. Add a ROA for AS393256, maxLength 18.673 of 673
Route object: none162.9.64.0/18No route object for it. A route object for 162.9.0.0/16 with origin AS393256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393256 in the RIR database for the space.673 of 673
ROA: none162.9.140.0/24No ROA covers it. Add a ROA for AS393256, maxLength 24.673 of 673
Route object: none162.9.140.0/24No route object for it. A route object for 162.9.0.0/16 with origin AS393256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393256 in the RIR database for the space.673 of 673
ROA: none162.9.0.0/17No ROA covers it. Add a ROA for AS393256, maxLength 17.670 of 673
Route object: none162.9.0.0/17No route object for it. A route object for 162.9.0.0/16 with origin AS393256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393256 in the RIR database for the space.670 of 673
ROA: none162.9.0.0/18No ROA covers it. Add a ROA for AS393256, maxLength 18.670 of 673
Route object: none162.9.0.0/18No route object for it. A route object for 162.9.0.0/16 with origin AS393256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393256 in the RIR database for the space.670 of 673
ROA: none162.9.140.0/23No ROA covers it. Add a ROA for AS393256, maxLength 23.670 of 673
Route object: none162.9.140.0/23No route object for it. A route object for 162.9.0.0/16 with origin AS393256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393256 in the RIR database for the space.670 of 673
ROA: none162.9.141.0/24No ROA covers it. Add a ROA for AS393256, maxLength 24.670 of 673
Route object: none162.9.141.0/24No route object for it. A route object for 162.9.0.0/16 with origin AS393256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393256 in the RIR database for the space.670 of 673
Route object: none2606:fec0:1::/48No route object for it. A route object for 2606:fec0::/32 with origin AS393256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393256 in the RIR database for the space.636 of 636
Route object: none2606:fec0:8000::/48No route object for it. A route object for 2606:fec0::/32 with origin AS393256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393256 in the RIR database for the space.636 of 636
Route object: none2606:fec0::/47No route object for it. A route object for 2606:fec0::/32 with origin AS393256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393256 in the RIR database for the space.635 of 636
Route object: none2606:fec0::/48No route object for it. A route object for 2606:fec0::/32 with origin AS393256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393256 in the RIR database for the space.635 of 636
Route object: none2606:fec0:8000::/47No route object for it. A route object for 2606:fec0::/32 with origin AS393256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393256 in the RIR database for the space.635 of 636
Route object: RIR204.124.152.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

162.9.0.0/16RADBNo ROA
2606:fec0::/32RADBValid

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.