bgpreport

Network · data from 2026-11-12

AS38813 Emantra Pty Ltd

Registry name: EMANTRA-AS-AP - Emantra Pty Ltd, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38813, 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.104.81.0/24 No ROA None 633 94% 67
103.104.82.0/24 Valid RIR databaseAPNIC 671 100% 67
103.104.83.0/24 Valid RIR databaseAPNIC 671 100% 67
111.118.209.0/24 Valid RIR databaseAPNIC 671 100% 67
111.118.210.0/24 Valid RIR databaseAPNIC 671 100% 67
111.118.211.0/24 Valid RIR databaseAPNIC 671 100% 67

AS-SET

AS38813'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 5 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none103.104.81.0/24No ROA covers it. Add a ROA for AS38813, maxLength 24.633 of 673
Route object: none103.104.81.0/24No route object for it. Add a route object with origin AS38813 in the RIR database for the space.633 of 673

Route objects not announced

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

111.118.208.0/24APNICValid
202.150.60.0/23RADBNo ROA
202.150.60.0/24APNICValid

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.