bgpreport

Network · data from 2026-11-12

AS50685 United Networks Ltd.

Registry name: UNITED-NETWORKS-AS United Networks Ltd., BY · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50685, 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.

93.125.39.0/24 No ROA RIR databaseRIPE 670 100% 68
93.125.42.0/24 No ROA RIR databaseRIPE 670 100% 68
93.125.49.0/24 No ROA RIR databaseRIPE 670 100% 68
93.170.236.0/24 Valid RIR databaseRIPE 670 100% 68
93.170.238.0/24 Valid RIR databaseRIPE 670 100% 68
93.170.239.0/24 Valid RIR databaseRIPE 670 100% 68
93.171.160.0/24 Valid RIR databaseRIPE 670 100% 68
93.171.161.0/24 Valid RIR databaseRIPE 670 100% 68
95.47.60.0/24 Valid RIR databaseRIPE 670 100% 68
95.47.61.0/24 Valid RIR databaseRIPE 670 100% 68
146.120.13.0/24 Valid RIR databaseRIPE 670 100% 68
146.120.14.0/24 Valid RIR databaseRIPE 670 100% 68
146.120.15.0/24 Valid RIR databaseRIPE 670 100% 68
146.120.192.0/24 Valid RIR databaseRIPE 670 100% 68
146.120.194.0/24 Valid RIR databaseRIPE 670 100% 68
146.120.195.0/24 Valid RIR databaseRIPE 670 100% 68
146.158.16.0/22 Valid RIR databaseRIPE 670 100% 68
93.170.237.0/24 Valid RIR databaseRIPE 669 99% 68
146.120.193.0/24 Valid RIR databaseRIPE 669 99% 68
2a02:128:9::/48 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS50685: RIPE::AS50685. 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 (AS50685 isn't in the set, or no route object for AS50685 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 objectsAS50685 in itNot covered
RIPE::AS50685 A single AS number, not a set: AS50685 (this network), 24 route objects.

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

  • ROA: none3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none93.125.39.0/24No ROA covers it. Add a ROA for AS50685, maxLength 24.670 of 673
ROA: none93.125.42.0/24No ROA covers it. Add a ROA for AS50685, maxLength 24.670 of 673
ROA: none93.125.49.0/24No ROA covers it. Add a ROA for AS50685, maxLength 24.670 of 673

Route objects not announced

Route objects with origin AS50685 whose prefix no peer sees AS50685 announce. Many are kept on purpose (backup routes, space announced only in some places).

93.171.160.0/23RIPEValid
95.47.60.0/23RIPEValid
146.120.14.0/23RIPEValid
146.120.192.0/22RIPEValid

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.