bgpreport

Network · data from 2026-11-12

AS37055 Emid (Pty) LTD

Registry name: IOCO Infrastructure Services (Pty) Ltd - IOCO Infrastructure Services (Pty) Ltd, ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37055, 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.164.116.0/22 Valid None 667 99% 67
41.222.228.0/23 Valid Nonecovered by 41.222.228.0/22 666 99% 67
41.222.230.0/23 Valid Other IRR onlyNTTCOM 666 99% 67
41.222.228.0/22 Valid RIR databaseAFRINIC 667 99% 67
41.223.252.0/22 Valid RIR databaseAFRINIC, NTTCOM 667 99% 67
169.255.116.0/22 Valid RIR databaseAFRINIC 667 99% 67
196.223.96.0/20 Valid RIR databaseAFRINIC 667 99% 67
197.231.168.0/21 Valid RIR databaseAFRINIC, NTTCOM 667 99% 67
197.157.242.0/23 Valid RIR databaseAFRINIC, NTTCOM 666 99% 67

AS-SET

AS37055'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 3 are in fix.csv.

  • Route object: none2
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: none102.164.116.0/22No route object for it. Add a route object with origin AS37055 in the RIR database for the space.667 of 673
Route object: none41.222.228.0/23No route object for it. A route object for 41.222.228.0/22 with origin AS37055 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37055 in the RIR database for the space.666 of 673
Route object: RIR41.222.230.0/23Route object only in NTTCOM. Add it in the RIR database for the space.666 of 673

Route objects not announced

Every route object with origin AS37055 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.