bgpreport

Network · data from 2026-11-12

AS55077 LightSpeed Technologies, LLC

Registry name: LIGHTSPEED-TECHNOLOGIES - LIGHT SPEED TECHNOLOGIES LLC, US · PeeringDB

5IPv4 routes 80.0% RPKI valid · 80.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
0Route objects not announced registered with origin AS55077, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55077, 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.
206.83.142.0/24 Invalid: origin Other origin only 2 0%low visibility 2
103.25.230.0/24 Valid RIR databaseARIN, RADB 673 100% 67
104.36.4.0/22 Valid RIR databaseARIN, RADB 673 100% 67
198.44.204.0/22 Valid RIR databaseARIN, RADB 673 100% 67
23.128.208.0/24 Valid RIR databaseARIN, RADB 671 100% 68
2602:ff31::/36 Valid RIR databaseARIN, RADB 604 95% 67

AS-SET

PeeringDB's irr_as_set for AS55077: RADB::AS55077:AS-CONE. 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 (AS55077 isn't in the set, or no route object for AS55077 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 objectsAS55077 in itNot covered
RADB::AS55077:AS-CONE RADB 115 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 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin206.83.142.0/24ROAs covering it name AS33175, not AS55077. If AS55077 should announce it, add a ROA for AS55077.2 of 673
Route object: none206.83.142.0/24Route objects for it name AS33175. Add a route object with origin AS55077 in the RIR database for the space.2 of 673

Route objects not announced

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