bgpreport

Network · data from 2026-11-12

AS18840 EQUIPOS Y SISTEMAS

Registry name: AS18840 - EQUIPOS Y SISTEMAS S.A., NI · PeeringDB

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

Announced routes

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

190.53.47.0/24 Invalid: origin Other origin only 11 2%low visibility 8
201.131.66.0/24 Invalid: origin Other origin only 11 2%low visibility 8
165.98.130.0/24 Invalid: origin Nonecovered by 165.98.128.0/22 7 1%low visibility 5
165.98.228.0/24 Invalid: origin Other origin only 7 1%low visibility 5
186.1.63.0/24 Valid Nonecovered by 186.1.56.0/21 673 100% 67
186.1.56.0/24 Valid Nonecovered by 186.1.56.0/21 672 100% 67
186.1.57.0/24 Valid Nonecovered by 186.1.56.0/21 672 100% 67
186.1.61.0/24 Valid Nonecovered by 186.1.56.0/21 672 100% 67
186.1.62.0/24 Valid Nonecovered by 186.1.56.0/21 672 100% 67
186.1.51.0/24 Valid Nonecovered by 186.1.48.0/21 667 99% 67
186.1.58.0/24 Valid Nonecovered by 186.1.56.0/21 667 99% 67
186.1.59.0/24 Valid Nonecovered by 186.1.56.0/21 667 99% 67
186.1.60.0/24 Valid Nonecovered by 186.1.56.0/21 667 99% 67
186.1.29.0/24 Valid Other IRR onlyRADB 673 100% 67
186.1.48.0/21 Valid Other IRR onlyRADB 673 100% 67
165.98.38.0/24 Valid Other IRR onlyRADB 672 100% 67
165.98.238.0/24 Valid Other IRR onlyRADB 672 100% 67
170.246.152.0/24 Valid Other IRR onlyRADB 672 100% 67
170.246.153.0/24 Valid Other IRR onlyRADB 672 100% 67
170.246.154.0/24 Valid Other IRR onlyRADB 672 100% 67
170.246.155.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.5.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.6.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.7.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.8.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.9.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.10.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.11.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.12.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.13.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.14.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.16.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.18.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.22.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.24.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.25.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.26.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.27.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.28.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.30.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.31.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.33.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.34.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.35.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.36.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.38.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.39.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.40.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.41.0/24 Valid Other IRR onlyRADB 672 100% 67
186.1.47.0/24 Valid Other IRR onlyRADB 672 100% 67
165.98.122.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.0.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.1.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.2.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.3.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.4.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.15.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.17.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.19.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.20.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.21.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.23.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.32.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.37.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.42.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.43.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.44.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.45.0/24 Valid Other IRR onlyRADB 667 99% 67
186.1.46.0/24 Valid Other IRR onlyRADB 667 99% 67
170.246.152.0/22 Valid RIR databaseLACNIC, RADB 673 100% 67
2800:8c0:10::/48 Valid RIR databaseLACNIC 635 100% 67
2800:8c0::/32 Valid RIR databaseLACNIC, RADB 630 99% 67

AS-SET

PeeringDB's irr_as_set for AS18840: RADB::AS18840:AS-TRANSIT. 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 (AS18840 isn't in the set, or no route object for AS18840 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 objectsAS18840 in itNot covered
RADB::AS18840:AS-TRANSIT RADB 5173 Yes 3

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

  • ROA: origin4
  • Route object: none13
  • Route object: RIR56
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: origin190.53.47.0/24ROAs covering it name AS263201, not AS18840. If AS18840 should announce it, add a ROA for AS18840.11 of 673
Route object: none190.53.47.0/24Route objects for it name AS263201. Add a route object with origin AS18840 in the RIR database for the space.11 of 673
ROA: origin201.131.66.0/24ROAs covering it name AS61513, not AS18840. If AS18840 should announce it, add a ROA for AS18840.11 of 673
Route object: none201.131.66.0/24Route objects for it name AS61513. Add a route object with origin AS18840 in the RIR database for the space.11 of 673
ROA: origin165.98.130.0/24ROAs covering it name AS25607, not AS18840. If AS18840 should announce it, add a ROA for AS18840.7 of 673
Route object: none165.98.130.0/24No route object for it. A route object for 165.98.128.0/22 with origin AS18840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18840 in the RIR database for the space.7 of 673
ROA: origin165.98.228.0/24ROAs covering it name AS25607, not AS18840. If AS18840 should announce it, add a ROA for AS18840.7 of 673
Route object: none165.98.228.0/24Route objects for it name AS25607. Add a route object with origin AS18840 in the RIR database for the space.7 of 673
Route object: none186.1.63.0/24No route object for it. A route object for 186.1.56.0/21 with origin AS18840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18840 in the RIR database for the space.673 of 673
Route object: none186.1.56.0/24No route object for it. A route object for 186.1.56.0/21 with origin AS18840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18840 in the RIR database for the space.672 of 673
Route object: none186.1.57.0/24No route object for it. A route object for 186.1.56.0/21 with origin AS18840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18840 in the RIR database for the space.672 of 673
Route object: none186.1.61.0/24No route object for it. A route object for 186.1.56.0/21 with origin AS18840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18840 in the RIR database for the space.672 of 673
Route object: none186.1.62.0/24No route object for it. A route object for 186.1.56.0/21 with origin AS18840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18840 in the RIR database for the space.672 of 673
Route object: none186.1.51.0/24No route object for it. A route object for 186.1.48.0/21 with origin AS18840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18840 in the RIR database for the space.667 of 673
Route object: none186.1.58.0/24No route object for it. A route object for 186.1.56.0/21 with origin AS18840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18840 in the RIR database for the space.667 of 673
Route object: none186.1.59.0/24No route object for it. A route object for 186.1.56.0/21 with origin AS18840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18840 in the RIR database for the space.667 of 673
Route object: none186.1.60.0/24No route object for it. A route object for 186.1.56.0/21 with origin AS18840 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18840 in the RIR database for the space.667 of 673
Route object: RIR186.1.29.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR186.1.48.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR165.98.38.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR165.98.238.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.246.152.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.246.153.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.246.154.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.246.155.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.5.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.6.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.7.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.8.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.9.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.10.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.11.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.12.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.13.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.14.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.16.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.18.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.22.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.24.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.25.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.26.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.27.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.28.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.30.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.31.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.33.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.34.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.35.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.36.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.38.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.39.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.40.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.41.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.1.47.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR165.98.122.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.0.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.1.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.2.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.3.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.4.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.15.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.17.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.19.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.20.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.21.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.23.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.32.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.37.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.42.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.43.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.44.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.45.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.1.46.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

165.98.76.0/24RADBNo ROA
165.98.112.0/24RADBNo ROA
165.98.128.0/22RADBNo ROA
165.98.184.0/24RADBNo ROA
165.98.185.0/24RADBNo ROA
165.98.187.0/24RADBNo ROA
165.98.188.0/24RADBNo ROA
165.98.248.0/24RADBValid
186.1.0.0/18LACNIC, RADBValid
186.1.56.0/21RADBValid

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.