bgpreport

Network · data from 2026-11-12

AS397867 DT-QC - Dissident Technologies integrateur en telecom incorporee

Registry name: DT-QC - Dissident Technologies integrateur en telecom incorporee, CA · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 100.0% with a route object
5IPv6 routes 0.0% RPKI valid · 40.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
7No 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 AS397867, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS397867, 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.
2605:8840:f00::/40 No ROA Nonecovered by 2605:8840::/32 636 100% 67
2605:8840:a101::/48 No ROA Nonecovered by 2605:8840::/32 636 100% 67
2605:8840:100::/48 No ROA Nonecovered by 2605:8840::/32 635 100% 67
23.148.16.0/24 No ROA Other IRR onlyRADB 671 100% 67
192.80.10.0/24 No ROA Other IRR onlyRADB 671 100% 67
2605:8840::/40 No ROA Other IRR onlyBELL 635 100% 69
2605:8840:1000::/40 No ROA Other IRR onlyBELL 635 100% 69

AS-SET

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

  • ROA: none7
  • Route object: none3
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2605:8840:f00::/40No ROA covers it. Add a ROA for AS397867, maxLength 40.636 of 636
Route object: none2605:8840:f00::/40No route object for it. A route object for 2605:8840::/32 with origin AS397867 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397867 in the RIR database for the space.636 of 636
ROA: none2605:8840:a101::/48No ROA covers it. Add a ROA for AS397867, maxLength 48.636 of 636
Route object: none2605:8840:a101::/48No route object for it. A route object for 2605:8840::/32 with origin AS397867 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397867 in the RIR database for the space.636 of 636
ROA: none2605:8840:100::/48No ROA covers it. Add a ROA for AS397867, maxLength 48.635 of 636
Route object: none2605:8840:100::/48No route object for it. A route object for 2605:8840::/32 with origin AS397867 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397867 in the RIR database for the space.635 of 636
ROA: none23.148.16.0/24No ROA covers it. Add a ROA for AS397867, maxLength 24.671 of 673
Route object: RIR23.148.16.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.80.10.0/24No ROA covers it. Add a ROA for AS397867, maxLength 24.671 of 673
Route object: RIR192.80.10.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2605:8840::/40No ROA covers it. Add a ROA for AS397867, maxLength 40.635 of 636
Route object: RIR2605:8840::/40Route object only in BELL. Add it in the RIR database for the space.635 of 636
ROA: none2605:8840:1000::/40No ROA covers it. Add a ROA for AS397867, maxLength 40.635 of 636
Route object: RIR2605:8840:1000::/40Route object only in BELL. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

2605:8840::/32RADBNo 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.