bgpreport

Network · data from 2026-11-12

AS199794 EMOCLOUD LTD

Registry name: EMO-AS EMOCLOUD LTD, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199794, 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.
2a0f:1cc6:b160::/44 Valid None 635 100% 67
91.200.222.0/24 Valid RIR databaseRIPE 671 100% 67
194.62.119.0/24 Valid RIR databaseRIPE 670 100% 67
2a0f:1cc6:fd00::/40 Valid RIR databaseRIPE 636 100% 69
2a0f:1cc6:ff00::/40 Valid RIR databaseRIPE 635 100% 69
2a0f:1cc6:fe00::/40 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS199794: AS199794:AS-EMOCLOUD. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS199794 isn't in the set, or no route object for AS199794 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS199794 in itNot covered
AS199794:AS-EMOCLOUD RIPE 115 Yes 1

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

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none2a0f:1cc6:b160::/44No route object for it. Add a route object with origin AS199794 in the RIR database for the space.635 of 636

Route objects not announced

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