bgpreport

Network · data from 2026-11-12

AS218887 E-GAUSS E-GAUSS LTD

Registry name: E-GAUSS E-GAUSS LTD, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS218887, 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.
212.134.98.0/24 Valid Other IRR onlyRADB 673 100% 66
81.5.161.0/24 Valid Other IRR onlyRADB 672 100% 66
5.199.43.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
5.199.58.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
51.194.94.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
87.254.20.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
147.125.168.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
179.61.236.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
185.139.0.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
185.150.136.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
212.74.56.0/24 Valid RIR databaseRADB, RIPE 673 100% 66

AS-SET

AS218887 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 2 are in fix.csv.

  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: RIR212.134.98.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR81.5.161.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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