bgpreport

Network · data from 2026-11-12

AS329793 ESURF SYSTEMS LIMITED - ESURF SYSTEMS LIMITED

Registry name: ESURF SYSTEMS LIMITED - ESURF SYSTEMS LIMITED, KE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS329793, 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.
102.201.148.0/22 No ROA RIR databaseAFRINIC 671 100% 68
102.201.148.0/24 No ROA RIR databaseAFRINIC 1 0%low visibility 3
102.201.149.0/24 No ROA RIR databaseAFRINIC 1 0%low visibility 3
102.201.150.0/24 No ROA RIR databaseAFRINIC 1 0%low visibility 3
102.201.151.0/24 No ROA RIR databaseAFRINIC 1 0%low visibility 3

AS-SET

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

  • ROA: none5
ChangePrefix or setDetailFull-table peers
ROA: none102.201.148.0/22No ROA covers it. Add a ROA for AS329793, maxLength 22.671 of 673
ROA: none102.201.148.0/24No ROA covers it. Add a ROA for AS329793, maxLength 24.1 of 673
ROA: none102.201.149.0/24No ROA covers it. Add a ROA for AS329793, maxLength 24.1 of 673
ROA: none102.201.150.0/24No ROA covers it. Add a ROA for AS329793, maxLength 24.1 of 673
ROA: none102.201.151.0/24No ROA covers it. Add a ROA for AS329793, maxLength 24.1 of 673

Route objects not announced

Every route object with origin AS329793 is announced.

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.