bgpreport

Network · data from 2026-11-12

AS201864 EdgeConnect

Registry name: as-trench MINHOCO 84 LIMITED, GB · PeeringDB

3IPv4 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 AS201864, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS201864, 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.
107.181.146.0/24 Valid RIR databaseRIPE 673 100% 67
146.19.138.0/24 Valid RIR databaseRIPE 673 100% 67
176.10.92.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS201864: AS201864:AS-TRENCH. 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 (AS201864 isn't in the set, or no route object for AS201864 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 objectsAS201864 in itNot covered
AS201864:AS-TRENCH RIPE 010 No 3

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.

  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
AS-SET: own ASNAS201864:AS-TRENCHAS201864 isn't in AS201864:AS-TRENCH (RIPE) once expanded. Add AS201864 to it.

Route objects not announced

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