bgpreport

Network · data from 2026-11-12

AS213900 RS Computers L.L.C

Registry name: rs RS Computers L.L.C, AL · PeeringDB

6IPv4 routes 83.3% RPKI valid · 83.3% with a route object
7IPv6 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
2Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS213900, seen from no peer

Announced routes

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

217.60.194.101/32 Invalid: maxLength Nonecovered by 217.60.194.0/24 1 0%low visibility 1
31.57.56.0/24 Valid RIR databaseALTDB, RIPE 672 100% 66
82.108.121.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
87.83.70.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
217.60.96.0/24 Valid RIR databaseALTDB, RIPE 672 100% 66
217.60.194.0/24 Valid RIR databaseRIPE 670 100% 68
2a14:7580:c000::/40 Valid RIR databaseALTDB, RIPE 634 100% 68
2a13:c8c3:a000::/36 Valid RIR databaseALTDB, RIPE 633 100% 68
2a13:c8c3:b000::/36 Valid RIR databaseALTDB, RIPE 633 100% 68
2a14:7583:200::/39 Valid RIR databaseRIPE 633 100% 68
2a13:c8c3:cf43::/48 Valid RIR databaseRIPE 632 99% 69
2a13:c8c3:e8ff::/48 Valid RIR databaseRIPE 632 99% 69
2a13:c8c3:cf44::/48 Valid RIR databaseRIPE 3 0%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS213900: AS213900:AS-DOWNSTREAMS. 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 (AS213900 isn't in the set, or no route object for AS213900 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 objectsAS213900 in itNot covered
AS213900:AS-DOWNSTREAMS RIPE3 member sets in no database: AS199746:AS-NEXTSERV, AS215110:AS-CUSTOMERS, AS39753:AS-LIUXYON 266936,659 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 8 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • AS-SET: missing member3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength217.60.194.101/32ROA 217.60.194.0/24 AS213900 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 217.60.194.101/32.1 of 673
Route object: none217.60.194.101/32No route object for it. A route object for 217.60.194.0/24 with origin AS213900 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS213900 in the RIR database for the space.1 of 673
AS-SET: missing memberAS213900:AS-DOWNSTREAMSAS213900:AS-DOWNSTREAMS (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.
AS-SET: missing memberAS213900:AS-DOWNSTREAMSAS213900:AS-DOWNSTREAMS (RIPE) lists AS215110:AS-CUSTOMERS; no IRR database read has it.
AS-SET: missing memberAS213900:AS-DOWNSTREAMSAS213900:AS-DOWNSTREAMS (RIPE) lists AS39753:AS-LIUXYON; no IRR database read has it.

Route objects not announced

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

2001:470:1f5::/48ARINValid
2a13:c8c3:cf41::/48RIPEValid
2a13:c8c3:cf42::/48RIPEValid

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.