bgpreport

Network · data from 2026-11-12

AS38714 E-Vision Internet

Registry name: EVISION-AS-AP - E-Vision Internet,, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38714, 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.
103.98.184.0/22 No ROA None 671 100% 67
118.82.41.0/24 No ROA Other IRR onlyRADB 672 100% 67
118.82.32.0/21 No ROA RIR databaseAPNIC, RADB 672 100% 67
118.82.34.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 67
118.82.40.0/23 No ROA RIR databaseAPNIC, RADB 672 100% 67
118.82.42.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 67
118.82.43.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 67
118.82.45.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 67
118.82.46.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 67

AS-SET

AS38714'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 36 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced25
ChangePrefix or setDetailFull-table peers
ROA: none103.98.184.0/22No ROA covers it. Add a ROA for AS38714, maxLength 22.671 of 673
Route object: none103.98.184.0/22No route object for it. Add a route object with origin AS38714 in the RIR database for the space.671 of 673
ROA: none118.82.41.0/24No ROA covers it. Add a ROA for AS38714, maxLength 24.672 of 673
Route object: RIR118.82.41.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none118.82.32.0/21No ROA covers it. Add a ROA for AS38714, maxLength 21.672 of 673
ROA: none118.82.34.0/24No ROA covers it. Add a ROA for AS38714, maxLength 24.672 of 673
ROA: none118.82.40.0/23No ROA covers it. Add a ROA for AS38714, maxLength 23.672 of 673
ROA: none118.82.42.0/24No ROA covers it. Add a ROA for AS38714, maxLength 24.672 of 673
ROA: none118.82.43.0/24No ROA covers it. Add a ROA for AS38714, maxLength 24.672 of 673
ROA: none118.82.45.0/24No ROA covers it. Add a ROA for AS38714, maxLength 24.672 of 673
ROA: none118.82.46.0/24No ROA covers it. Add a ROA for AS38714, maxLength 24.672 of 673

Route objects not announced

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

118.82.32.0/20RADBNo ROA
118.82.32.0/22RADBNo ROA
118.82.32.0/23RADBNo ROA
118.82.32.0/24RADBNo ROA
118.82.33.0/24RADBNo ROA
118.82.34.0/23RADBNo ROA
118.82.35.0/24RADBNo ROA
118.82.36.0/22RADBNo ROA
118.82.36.0/23RADBNo ROA
118.82.36.0/24RADBNo ROA
118.82.37.0/24RADBNo ROA
118.82.38.0/23RADBNo ROA
118.82.38.0/24RADBNo ROA
118.82.39.0/24RADBNo ROA
118.82.40.0/21RADBNo ROA
118.82.40.0/22RADBNo ROA
118.82.40.0/24RADBNo ROA
118.82.42.0/23RADBNo ROA
118.82.44.0/23RADBNo ROA
118.82.44.0/24APNIC, RADBNo ROA
118.82.46.0/23RADBNo ROA
118.82.47.0/24APNIC, RADBNo ROA
203.27.60.0/24RADBNo ROA
203.32.78.0/24RADBNo ROA
203.32.79.0/24RADBNo 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.