bgpreport

Network · data from 2026-11-12

AS8002 Stealth Communications

Registry name: STEALTH - Stealth Communications Services, LLC, US · PeeringDB

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

Announced routes

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

207.251.68.128/27 Invalid: maxLength Nonecovered by 207.251.64.0/18 1 0%low visibility 1
207.251.68.192/27 Invalid: maxLength Nonecovered by 207.251.64.0/18 1 0%low visibility 1
192.68.29.0/24 No ROA Other IRR onlyRADB 673 100% 67
206.252.192.0/19 Valid Other IRR onlyRADB 673 100% 67
207.251.64.0/18 Valid Other IRR onlyRADB 673 100% 67
2001:458::/32 Valid Other IRR onlyRADB 635 100% 69
207.251.86.0/24 Valid RIR databaseARIN, RADB 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS8002: AS-STEALTH. 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 (AS8002 isn't in the set, or no route object for AS8002 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 objectsAS8002 in itNot covered
AS-STEALTH RADB 24732,914 Yes 2
RIPE (also)lists itself further down2 member sets in no database: AS-TSL37343, AS142594:AS-SPEEDYPAGE 151361,569 No 7

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

  • ROA: maxLength2
  • ROA: none1
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: maxLength207.251.68.128/27ROA 207.251.64.0/18 AS8002 has maxLength 18; the route is a /27. Raise the maxLength, or add a ROA for 207.251.68.128/27.1 of 673
Route object: none207.251.68.128/27No route object for it. A route object for 207.251.64.0/18 with origin AS8002 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS8002 in the RIR database for the space.1 of 673
ROA: maxLength207.251.68.192/27ROA 207.251.64.0/18 AS8002 has maxLength 18; the route is a /27. Raise the maxLength, or add a ROA for 207.251.68.192/27.1 of 673
Route object: none207.251.68.192/27No route object for it. A route object for 207.251.64.0/18 with origin AS8002 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS8002 in the RIR database for the space.1 of 673
ROA: none192.68.29.0/24No ROA covers it. Add a ROA for AS8002, maxLength 24.673 of 673
Route object: RIR192.68.29.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR206.252.192.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR207.251.64.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2001:458::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

63.148.46.0/24RADBNo ROA
63.239.204.0/23RADBNo ROA
168.245.226.0/24RADBNo ROA
207.251.65.0/24ARIN, RADBValid

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.