bgpreport

Network · data from 2026-11-12

AS59993 UNLIMITED IS LIMITED, LLC

Registry name: UILLLC-20230328 UNLIMITED IS LIMITED, LLC, US · PeeringDB

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

Announced routes

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

151.243.100.0/24 Invalid: origin Other origin only 2 0%low visibility 2
23.153.232.0/24 Valid RIR databaseARIN, RADB 672 100% 70
194.169.172.0/24 Valid RIR databaseRADB, RIPE 672 100% 70

AS-SET

PeeringDB's irr_as_set for AS59993: RIPE::AS59993:AS-ALL. 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 (AS59993 isn't in the set, or no route object for AS59993 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 objectsAS59993 in itNot covered
RIPE::AS59993:AS-ALL RIPE 118 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 8 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin151.243.100.0/24ROAs covering it name AS834, not AS59993. If AS59993 should announce it, add a ROA for AS59993.2 of 673
Route object: none151.243.100.0/24Route objects for it name AS834. Add a route object with origin AS59993 in the RIR database for the space.2 of 673

Route objects not announced

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

192.75.196.0/23RADBValid
2602:fa9b:c0::/48ARINValid
2a07:54c0:ffee::/48RIPEValid
2a0d:2585::/32RADB, RIPEValid
2a0d:2585:e000::/35RADBValid
2a13:9500:47::/48RIPEValid

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.