bgpreport

Network · data from 2026-11-12

AS395471 Data@ccess Communication

Registry name: DATACCESSPR - Data@ccess Communication, Inc., PR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS395471, 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.
207.150.246.0/24 No ROA Other origin only 667 99% 68
70.35.134.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
207.150.245.0/24 No ROA RIR databaseARIN 673 100% 67
67.215.101.0/24 No ROA RIR databaseARIN 667 99% 68
70.35.130.0/24 No ROA RIR databaseARIN, RADB 667 99% 68
70.35.131.0/24 No ROA RIR databaseARIN 667 99% 68
70.35.133.0/24 No ROA RIR databaseARIN 667 99% 68
70.35.135.0/24 No ROA RIR databaseARIN, RADB 667 99% 68
70.35.136.0/24 No ROA RIR databaseARIN, RADB 667 99% 68
70.35.139.0/24 No ROA RIR databaseARIN, RADB 667 99% 68
70.35.140.0/24 No ROA RIR databaseARIN, RADB 667 99% 68
70.35.141.0/24 No ROA RIR databaseARIN, RADB 667 99% 68

AS-SET

AS395471's PeeringDB record names no 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 18 are in fix.csv.

  • ROA: none12
  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none207.150.246.0/24No ROA covers it. Add a ROA for AS395471, maxLength 24.667 of 673
Route object: none207.150.246.0/24Route objects for it name AS18895. Add a route object with origin AS395471 in the RIR database for the space.667 of 673
ROA: none70.35.134.0/24No ROA covers it. Add a ROA for AS395471, maxLength 24.673 of 673
ROA: none207.150.245.0/24No ROA covers it. Add a ROA for AS395471, maxLength 24.673 of 673
ROA: none67.215.101.0/24No ROA covers it. Add a ROA for AS395471, maxLength 24.667 of 673
ROA: none70.35.130.0/24No ROA covers it. Add a ROA for AS395471, maxLength 24.667 of 673
ROA: none70.35.131.0/24No ROA covers it. Add a ROA for AS395471, maxLength 24.667 of 673
ROA: none70.35.133.0/24No ROA covers it. Add a ROA for AS395471, maxLength 24.667 of 673
ROA: none70.35.135.0/24No ROA covers it. Add a ROA for AS395471, maxLength 24.667 of 673
ROA: none70.35.136.0/24No ROA covers it. Add a ROA for AS395471, maxLength 24.667 of 673
ROA: none70.35.139.0/24No ROA covers it. Add a ROA for AS395471, maxLength 24.667 of 673
ROA: none70.35.140.0/24No ROA covers it. Add a ROA for AS395471, maxLength 24.667 of 673
ROA: none70.35.141.0/24No ROA covers it. Add a ROA for AS395471, maxLength 24.667 of 673

Route objects not announced

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

24.139.169.0/24RADBNo ROA
64.185.192.0/19RADBNo ROA
173.228.213.0/24RADBNo ROA
173.228.214.0/24RADBNo ROA
2607:a380::/32ARINNo 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.