bgpreport

Network · data from 2026-11-12

AS27988 Servicios y Telecomunicaciones

Registry name: AS27988 - Servicios y Telecomunicaciones S.A., AR · PeeringDB

30IPv4 routes 100.0% RPKI valid · 96.7% with a route object
6IPv6 routes 100.0% RPKI valid · 16.7% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 6 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
11Route objects not announced registered with origin AS27988, seen from no peer

Announced routes

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

200.55.246.0/23 Valid Nonecovered by 200.55.240.0/21 670 100% 67
2803:8d00:b000::/48 Valid Nonecovered by 2803:8d00::/32 633 100% 67
2803:8d00:2::/48 Valid Nonecovered by 2803:8d00::/32 631 99% 67
2803:8d00:f136::/48 Valid Nonecovered by 2803:8d00::/32 630 99% 67
2803:8d00:f137::/48 Valid Nonecovered by 2803:8d00::/32 630 99% 67
2803:8d00:f135::/48 Valid Nonecovered by 2803:8d00::/32 318 50% 64
198.12.36.0/23 Valid Other IRR onlyALTDB, RADB 673 100% 66
190.122.82.0/23 Valid Other IRR onlyALTDB, RADB 672 100% 67
198.12.38.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 66
190.122.80.0/23 Valid Other IRR onlyALTDB, RADB 671 100% 67
190.122.84.0/23 Valid Other IRR onlyALTDB, RADB 671 100% 67
190.122.86.0/23 Valid Other IRR onlyRADB 671 100% 67
190.122.92.0/23 Valid Other IRR onlyALTDB, RADB 671 100% 66
190.122.93.0/24 Valid Other IRR onlyALTDB, RADB 671 100% 67
190.122.95.0/24 Valid Other IRR onlyALTDB, RADB 671 100% 67
200.55.243.0/24 Valid Other IRR onlyALTDB, RADB 671 100% 66
190.122.88.0/23 Valid Other IRR onlyRADB 670 100% 67
200.55.240.0/23 Valid Other IRR onlyALTDB, RADB 670 100% 67
200.55.244.0/23 Valid Other IRR onlyRADB 670 100% 67
190.122.86.0/24 Valid Other IRR onlyALTDB, RADB 669 99% 67
190.122.81.0/24 Valid Other IRR onlyALTDB, RADB 668 99% 66
190.122.80.0/24 Valid Other IRR onlyALTDB, RADB 98 15% 37
190.122.84.0/24 Valid Other IRR onlyALTDB, RADB 98 15% 37
190.122.85.0/24 Valid Other IRR onlyALTDB, RADB 98 15% 37
190.122.92.0/24 Valid Other IRR onlyALTDB, RADB 98 15% 37
200.55.240.0/24 Valid Other IRR onlyALTDB, RADB 98 15% 37
200.55.241.0/24 Valid Other IRR onlyALTDB, RADB 98 15% 37
200.55.245.0/24 Valid Other IRR onlyALTDB, RADB 98 15% 37
200.55.247.0/24 Valid Other IRR onlyALTDB, RADB 98 15% 37
190.122.82.0/24 Valid Other IRR onlyALTDB, RADB 97 14% 37
190.122.87.0/24 Valid Other IRR onlyALTDB, RADB 23 3%low visibility 11
198.12.37.0/24 Valid Other IRR onlyALTDB, RADB 23 3%low visibility 11
200.55.244.0/24 Valid Other IRR onlyALTDB, RADB 23 3%low visibility 11
200.55.246.0/24 Valid Other IRR onlyALTDB, RADB 23 3%low visibility 11
189.90.228.0/23 Valid RIR databaseLACNIC, RADB 671 100% 67
2803:8d00::/32 Valid RIR databaseALTDB, LACNIC, RADB 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS27988: AS27988:AS-CUSTOMERS. 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 (AS27988 isn't in the set, or no route object for AS27988 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 objectsAS27988 in itNot covered
AS27988:AS-CUSTOMERS RADB 4123,100 Yes 0
ALTDB (also) 241307 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 45 are in fix.csv.

  • Route object: none6
  • Route object: RIR28
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
Route object: none200.55.246.0/23No route object for it. A route object for 200.55.240.0/21 with origin AS27988 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27988 in the RIR database for the space.670 of 673
Route object: none2803:8d00:b000::/48No route object for it. A route object for 2803:8d00::/32 with origin AS27988 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27988 in the RIR database for the space.633 of 636
Route object: none2803:8d00:2::/48No route object for it. A route object for 2803:8d00::/32 with origin AS27988 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27988 in the RIR database for the space.631 of 636
Route object: none2803:8d00:f136::/48No route object for it. A route object for 2803:8d00::/32 with origin AS27988 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27988 in the RIR database for the space.630 of 636
Route object: none2803:8d00:f137::/48No route object for it. A route object for 2803:8d00::/32 with origin AS27988 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27988 in the RIR database for the space.630 of 636
Route object: none2803:8d00:f135::/48No route object for it. A route object for 2803:8d00::/32 with origin AS27988 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27988 in the RIR database for the space.318 of 636
Route object: RIR198.12.36.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR190.122.82.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR198.12.38.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.122.80.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.122.84.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.122.86.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.122.92.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.122.93.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.122.95.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.55.243.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.122.88.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR200.55.240.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR200.55.244.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.122.86.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR190.122.81.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR190.122.80.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.98 of 673
Route object: RIR190.122.84.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.98 of 673
Route object: RIR190.122.85.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.98 of 673
Route object: RIR190.122.92.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.98 of 673
Route object: RIR200.55.240.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.98 of 673
Route object: RIR200.55.241.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.98 of 673
Route object: RIR200.55.245.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.98 of 673
Route object: RIR200.55.247.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.98 of 673
Route object: RIR190.122.82.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.97 of 673
Route object: RIR190.122.87.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.23 of 673
Route object: RIR198.12.37.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.23 of 673
Route object: RIR200.55.244.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.23 of 673
Route object: RIR200.55.246.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.23 of 673

Route objects not announced

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

189.90.228.0/24RADBValid
189.90.229.0/24RADBValid
190.122.80.0/20ALTDB, LACNIC, RADBValid
190.122.83.0/24ALTDB, RADBValid
190.122.88.0/24ALTDB, RADBValid
190.122.89.0/24ALTDB, RADBValid
198.12.36.0/22ALTDB, LACNICValid
198.12.36.0/24ALTDB, RADBValid
198.12.38.0/23ALTDBValid
200.55.240.0/21ALTDB, LACNIC, RADBValid
200.55.242.0/24ALTDB, RADBValid

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.