bgpreport

Network · data from 2026-11-12

AS397700 LXXIX Project Lab LLC

Registry name: LXXIX-PROJECT-LAB-01 - LXXIX Project Lab LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS397700, 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.
79.172.201.0/24 Valid Nonecovered by 79.172.200.0/23 673 100% 67
79.172.200.0/24 Valid Nonecovered by 79.172.200.0/23 671 100% 67
23.188.24.0/24 Valid RIR databaseALTDB, ARIN, RADB 673 100% 67
79.172.200.0/23 Valid RIR databaseALTDB, RADB, RIPE 671 100% 67
192.35.249.0/24 Valid RIR databaseARIN 671 100% 67
74.50.0.0/24 Valid RIR databaseALTDB, ARIN, RADB 670 100% 67
2602:f826::/36 Valid RIR databaseALTDB, ARIN, RADB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS397700: AS397700:AS-LXXIX. 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 (AS397700 isn't in the set, or no route object for AS397700 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 objectsAS397700 in itNot covered
AS397700:AS-LXXIX ARIN 116 Yes 0

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

  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none79.172.201.0/24No route object for it. A route object for 79.172.200.0/23 with origin AS397700 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397700 in the RIR database for the space.673 of 673
Route object: none79.172.200.0/24No route object for it. A route object for 79.172.200.0/23 with origin AS397700 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397700 in the RIR database for the space.671 of 673

Route objects not announced

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

38.81.116.0/24ALTDB, RADBNo 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.