bgpreport

Network · data from 2026-11-12

AS393950 Xiber

Registry name: XIBER-LLC - Xiber, US · PeeringDB

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

Announced routes

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

2604:50::/48 No ROA Other IRR onlyRADB 635 100% 69
2604:50:2::/48 No ROA Other IRR onlyRADB 634 100% 69
2604:50:9::/48 No ROA Other IRR onlyRADB 329 52% 64
2604:50:1::/48 No ROA Other IRR onlyRADB 2 0%low visibility 2
2604:50:8::/48 No ROA Other IRR onlyRADB 1 0%low visibility 1
69.36.6.0/24 Valid Nonecovered by 69.36.0.0/20 671 100% 68
107.181.32.0/24 Valid Other IRR onlyRADB 673 100% 67
69.36.0.0/20 Valid Other IRR onlyRADB 671 100% 68
69.36.14.0/24 Valid Other IRR onlyRADB 671 100% 68
69.36.15.0/24 Valid Other IRR onlyRADB 671 100% 68
104.167.32.0/20 Valid Other IRR onlyRADB 671 100% 68
104.251.160.0/22 Valid Other IRR onlyRADB 671 100% 68
104.251.168.0/22 Valid Other IRR onlyRADB 671 100% 68
104.251.174.0/23 Valid Other IRR onlyRADB 671 100% 68
172.98.132.0/24 Valid Other IRR onlyRADB 671 100% 68
172.98.133.0/24 Valid Other IRR onlyRADB 671 100% 68
172.98.134.0/24 Valid Other IRR onlyRADB 671 100% 68
172.98.135.0/24 Valid Other IRR onlyRADB 671 100% 68
172.98.136.0/24 Valid Other IRR onlyRADB 671 100% 68
172.98.140.0/22 Valid Other IRR onlyRADB 671 100% 68
192.81.0.0/24 Valid Other IRR onlyRADB 671 100% 68
192.81.1.0/24 Valid Other IRR onlyRADB 671 100% 68
192.81.2.0/24 Valid Other IRR onlyRADB 671 100% 68
192.81.4.0/22 Valid Other IRR onlyRADB 671 100% 68
104.251.164.0/24 Valid Other IRR onlyRADB 670 100% 67
172.98.137.0/24 Valid Other IRR onlyRADB 669 99% 68
172.98.138.0/24 Valid Other IRR onlyRADB 668 99% 67
172.98.139.0/24 Valid Other IRR onlyRADB 668 99% 67
192.81.3.0/24 Valid Other IRR onlyRADB 668 99% 67
172.98.129.0/24 Valid RIR databaseARIN, RADB 671 100% 68
172.98.130.0/23 Valid RIR databaseARIN, RADB 671 100% 68
172.98.128.0/24 Valid RIR databaseARIN, RADB 670 100% 68
2604:50:4::/48 Valid RIR databaseARIN, RADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS393950: AS-XIBER. 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 (AS393950 isn't in the set, or no route object for AS393950 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 objectsAS393950 in itNot covered
AS-XIBER RADB 61388 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 54 are in fix.csv.

  • ROA: none5
  • Route object: none1
  • Route object: RIR28
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
ROA: none2604:50::/48No ROA covers it. Add a ROA for AS393950, maxLength 48.635 of 636
Route object: RIR2604:50::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2604:50:2::/48No ROA covers it. Add a ROA for AS393950, maxLength 48.634 of 636
Route object: RIR2604:50:2::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2604:50:9::/48No ROA covers it. Add a ROA for AS393950, maxLength 48.329 of 636
Route object: RIR2604:50:9::/48Route object only in RADB. Add it in the RIR database for the space.329 of 636
ROA: none2604:50:1::/48No ROA covers it. Add a ROA for AS393950, maxLength 48.2 of 636
Route object: RIR2604:50:1::/48Route object only in RADB. Add it in the RIR database for the space.2 of 636
ROA: none2604:50:8::/48No ROA covers it. Add a ROA for AS393950, maxLength 48.1 of 636
Route object: RIR2604:50:8::/48Route object only in RADB. Add it in the RIR database for the space.1 of 636
Route object: none69.36.6.0/24No route object for it. A route object for 69.36.0.0/20 with origin AS393950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393950 in the RIR database for the space.671 of 673
Route object: RIR107.181.32.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR69.36.0.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.36.14.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.36.15.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR104.167.32.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR104.251.160.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR104.251.168.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR104.251.174.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR172.98.132.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR172.98.133.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR172.98.134.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR172.98.135.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR172.98.136.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR172.98.140.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.81.0.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.81.1.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.81.2.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.81.4.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR104.251.164.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR172.98.137.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR172.98.138.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR172.98.139.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR192.81.3.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

104.251.164.0/22RADBValid
104.251.165.0/24RADBValid
104.251.166.0/24RADBValid
104.251.167.0/24RADBValid
104.251.168.0/24RADBValid
107.181.33.0/24RADBValid
107.181.34.0/24RADBValid
107.181.35.0/24RADBValid
107.181.36.0/22RADBValid
107.181.40.0/21RADBValid
172.98.132.0/22ARINValid
172.98.136.0/21ARINValid
172.98.140.0/23RADBValid
172.98.142.0/23RADBValid
2001:470:32f::/48ARINValid
2001:470:333::/48ARINValid
2001:470:35e::/48ARINValid
2604:50::/32BBOINo ROA
2604:50:5::/48RADBNo ROA
2604:50:7::/48RADBNo 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.