bgpreport

Network · data from 2026-11-12

AS40076 DOVETEL - DOVETEL COMMUNICATIONS, LLC.

Registry name: DOVETEL - DOVETEL COMMUNICATIONS, LLC., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS40076, 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.
161.210.4.0/22 No ROA RIR databaseARIN, RADB 671 100% 68
199.16.176.0/22 No ROA RIR databaseARIN, RADB 671 100% 68
199.115.120.0/22 No ROA RIR databaseARIN, RADB 671 100% 68
208.71.48.0/22 No ROA RIR databaseARIN, BBOI, RADB 671 100% 68
208.73.80.0/21 No ROA RIR databaseARIN, BBOI, RADB 671 100% 68
162.213.56.0/22 No ROA RIR databaseARIN 668 99% 68
2607:fed0::/32 No ROA RIR databaseARIN, RADB 634 100% 70

AS-SET

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

  • ROA: none7
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none161.210.4.0/22No ROA covers it. Add a ROA for AS40076, maxLength 22.671 of 673
ROA: none199.16.176.0/22No ROA covers it. Add a ROA for AS40076, maxLength 22.671 of 673
ROA: none199.115.120.0/22No ROA covers it. Add a ROA for AS40076, maxLength 22.671 of 673
ROA: none208.71.48.0/22No ROA covers it. Add a ROA for AS40076, maxLength 22.671 of 673
ROA: none208.73.80.0/21No ROA covers it. Add a ROA for AS40076, maxLength 21.671 of 673
ROA: none162.213.56.0/22No ROA covers it. Add a ROA for AS40076, maxLength 22.668 of 673
ROA: none2607:fed0::/32No ROA covers it. Add a ROA for AS40076, maxLength 32.634 of 636

Route objects not announced

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

72.162.92.0/23BBOIInvalid: origin
136.228.177.0/24RADBNo ROA
161.210.4.0/24RADBNo ROA
161.210.5.0/24RADBNo ROA
161.210.6.0/24RADBNo ROA
161.210.7.0/24RADBNo ROA
199.182.56.0/22RADBNo ROA
204.27.160.0/24RADBNo ROA
204.155.48.0/21RADBNo ROA
204.155.56.0/22BBOI, RADBNo 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.