bgpreport

Network · data from 2026-11-12

AS263715 EMPRESA DE SERVICIOS Y APLICACIONES TECNOLOGICAS SRL

Registry name: AS263715 - EMPRESA DE SERVICIOS Y APLICACIONES TECNOLOGICAS SRL, AR · PeeringDB

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

Announced routes

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

131.255.181.0/24 Valid Nonecovered by 131.255.180.0/22 99 15% 39
131.255.182.0/24 Valid Nonecovered by 131.255.180.0/22 99 15% 39
131.255.183.0/24 Valid Nonecovered by 131.255.180.0/22 99 15% 39
138.186.216.0/24 Valid Nonecovered by 138.186.216.0/22 99 15% 39
138.186.217.0/24 Valid Nonecovered by 138.186.216.0/22 99 15% 39
138.186.218.0/24 Valid Nonecovered by 138.186.216.0/22 99 15% 39
138.186.219.0/24 Valid Nonecovered by 138.186.216.0/22 99 15% 39
131.255.180.0/24 Valid Other IRR onlyRADB 100 15% 39
131.255.180.0/22 Valid RIR databaseLACNIC, RADB 667 99% 67
138.186.216.0/22 Valid RIR databaseLACNIC 667 99% 67

AS-SET

PeeringDB's irr_as_set for AS263715: AS-ESAT. 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 (AS263715 isn't in the set, or no route object for AS263715 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 objectsAS263715 in itNot covered
AS-ESAT In no IRR database read today.

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

  • Route object: none7
  • Route object: RIR1
  • AS-SET: not found1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none131.255.181.0/24No route object for it. A route object for 131.255.180.0/22 with origin AS263715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263715 in the RIR database for the space.99 of 673
Route object: none131.255.182.0/24No route object for it. A route object for 131.255.180.0/22 with origin AS263715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263715 in the RIR database for the space.99 of 673
Route object: none131.255.183.0/24No route object for it. A route object for 131.255.180.0/22 with origin AS263715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263715 in the RIR database for the space.99 of 673
Route object: none138.186.216.0/24No route object for it. A route object for 138.186.216.0/22 with origin AS263715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263715 in the RIR database for the space.99 of 673
Route object: none138.186.217.0/24No route object for it. A route object for 138.186.216.0/22 with origin AS263715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263715 in the RIR database for the space.99 of 673
Route object: none138.186.218.0/24No route object for it. A route object for 138.186.216.0/22 with origin AS263715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263715 in the RIR database for the space.99 of 673
Route object: none138.186.219.0/24No route object for it. A route object for 138.186.216.0/22 with origin AS263715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263715 in the RIR database for the space.99 of 673
Route object: RIR131.255.180.0/24Route object only in RADB. Add it in the RIR database for the space.100 of 673
AS-SET: not foundAS-ESATPeeringDB names AS-ESAT; no IRR database read has it.

Route objects not announced

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

2803:2780::/32RADBNo 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.