bgpreport

Network · data from 2026-11-12

AS8095 LIGHTSTACKGLOBAL - LightStack Global LLC

Registry name: LIGHTSTACKGLOBAL - LightStack Global LLC, US · not in PeeringDB

36IPv4 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
20Route objects not announced registered with origin AS8095, seen from no peer

Announced routes

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

23.133.84.0/24 Valid RIR databaseARIN, NTTCOM 673 100% 70
23.182.104.0/24 Valid RIR databaseARIN, NTTCOM 673 100% 70
23.149.4.0/24 Valid RIR databaseARIN 671 100% 67
23.155.248.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.157.72.0/24 Valid RIR databaseARIN 671 100% 67
23.178.8.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.178.104.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.178.200.0/24 Valid RIR databaseARIN 671 100% 67
23.178.216.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.178.232.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.179.8.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.179.56.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.179.72.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.179.88.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.179.120.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.179.136.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.179.152.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.179.200.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.180.8.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.180.40.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.180.56.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.180.72.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.180.152.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.180.168.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.180.216.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.180.232.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.181.8.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.181.40.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.181.152.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.181.184.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.181.200.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.181.216.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.181.232.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.181.248.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.182.136.0/24 Valid RIR databaseARIN, NTTCOM 671 100% 67
23.188.88.0/24 Valid RIR databaseARIN, RADB 671 100% 67

AS-SET

AS8095 isn't in PeeringDB, where networks name their AS-SET.

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

  • Route object: not announced20

Route objects not announced

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

23.154.120.0/24ARIN, NTTCOMValid
23.154.152.0/24ARIN, NTTCOMValid
23.154.200.0/24ARIN, NTTCOMValid
23.154.216.0/24ARIN, NTTCOMValid
23.155.104.0/24ARIN, NTTCOMValid
23.155.120.0/24ARIN, NTTCOMValid
23.155.232.0/24ARIN, NTTCOMValid
23.156.8.0/24ARIN, NTTCOMValid
23.181.88.0/24ARINValid
23.182.40.0/24ARIN, NTTCOMValid
66.79.175.0/24NTTCOMNo ROA
66.79.177.0/24NTTCOMNo ROA
204.128.56.0/21ARIN, NTTCOMValid
205.209.129.0/24NTTCOMNo ROA
205.209.134.0/24NTTCOMNo ROA
2602:2e3::/40NTTCOMNo ROA
2602:f70e::/40NTTCOMNo ROA
2602:fed2:7e02::/48NTTCOMNo ROA
2602:fed2:7e82::/48NTTCOMNo ROA
2605:f200::/32NTTCOMNo ROA

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.