bgpreport

Network · data from 2026-11-12

AS48399 Linxdatacenter

Registry name: AS-LINXDATACENTER Svyaz VSD LLC, RU · PeeringDB

14IPv4 routes 92.9% RPKI valid · 92.9% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 0 origin · 1 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 AS48399, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS48399, 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.
192.70.196.193/32 Invalid: maxLength Nonecovered by 192.70.196.0/23 2 0%low visibility 6
85.193.70.0/23 Valid RIR databaseRIPE 673 100% 66
91.188.246.0/23 Valid RIR databaseRIPE 673 100% 66
130.49.164.0/23 Valid RIR databaseRIPE 673 100% 66
130.49.166.0/23 Valid RIR databaseRIPE 673 100% 66
178.170.223.0/24 Valid RIR databaseRIPE 673 100% 66
185.190.116.0/23 Valid RIR databaseRIPE 673 100% 66
185.190.118.0/23 Valid RIR databaseRIPE 673 100% 66
192.70.196.0/23 Valid RIR databaseRIPE 673 100% 66
192.70.198.0/23 Valid RIR databaseRIPE 673 100% 66
45.15.254.0/24 Valid RIR databaseRIPE 672 100% 66
45.93.13.0/24 Valid RIR databaseRIPE 672 100% 66
45.147.195.0/24 Valid RIR databaseRIPE 672 100% 66
77.83.72.0/24 Valid RIR databaseRIPE 672 100% 66
2a07:ecc0::/30 Valid RIR databaseRIPE 635 100% 67
2a07:ecc4::/30 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS48399: AS-LINXDATACENTER. 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 (AS48399 isn't in the set, or no route object for AS48399 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 objectsAS48399 in itNot covered
AS-LINXDATACENTER RIPE 304162 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: maxLength1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: maxLength192.70.196.193/32ROA 192.70.196.0/23 AS48399 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 192.70.196.193/32.2 of 673
Route object: none192.70.196.193/32No route object for it. A route object for 192.70.196.0/23 with origin AS48399 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS48399 in the RIR database for the space.2 of 673

Route objects not announced

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