bgpreport

Network · data from 2026-11-12

AS28103 TEISA

Registry name: AS28103 - TECNOLOGIA EN ELECTRONICA E INFORMATICA SOCIEDAD ANONIMA (T.E.I.S.A), PY · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28103, 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.161.252.0/24 Valid RIR databaseLACNIC, RADB 673 100% 70
131.161.253.0/24 Valid RIR databaseLACNIC, RADB 673 100% 70
131.161.254.0/24 Valid RIR databaseLACNIC, RADB 673 100% 70
131.161.255.0/24 Valid RIR databaseLACNIC, RADB 673 100% 70
138.186.60.0/24 Valid RIR databaseLACNIC, RADB 673 100% 70
138.186.61.0/24 Valid RIR databaseLACNIC, RADB 673 100% 70
138.186.62.0/24 Valid RIR databaseLACNIC, RADB 673 100% 70
138.186.63.0/24 Valid RIR databaseLACNIC, RADB 673 100% 70
179.189.218.0/24 Valid RIR databaseLACNIC, RADB 673 100% 70
179.189.219.0/24 Valid RIR databaseLACNIC, RADB 673 100% 70
190.110.226.0/24 Valid RIR databaseLACNIC, RADB 673 100% 70
190.110.227.0/24 Valid RIR databaseLACNIC, RADB 673 100% 70
190.110.230.0/24 Valid RIR databaseLACNIC 673 100% 70
190.110.231.0/24 Valid RIR databaseLACNIC 673 100% 70
190.110.246.0/24 Valid RIR databaseLACNIC 673 100% 70
190.110.247.0/24 Valid RIR databaseLACNIC 673 100% 70
190.211.240.0/24 Valid RIR databaseLACNIC 673 100% 70
190.211.241.0/24 Valid RIR databaseLACNIC 673 100% 70
190.211.242.0/24 Valid RIR databaseLACNIC 673 100% 70
190.211.243.0/24 Valid RIR databaseLACNIC 673 100% 70
200.123.37.0/24 Valid RIR databaseLACNIC 673 100% 70
200.123.59.0/24 Valid RIR databaseLACNIC 673 100% 70
200.123.61.0/24 Valid RIR databaseLACNIC 673 100% 70
201.222.48.0/24 Valid RIR databaseLACNIC 673 100% 70
201.222.49.0/24 Valid RIR databaseLACNIC 673 100% 70
201.222.50.0/24 Valid RIR databaseLACNIC 673 100% 70
201.222.51.0/24 Valid RIR databaseLACNIC 673 100% 70
201.222.52.0/24 Valid RIR databaseLACNIC 673 100% 70
201.222.53.0/24 Valid RIR databaseLACNIC 673 100% 70
201.222.54.0/24 Valid RIR databaseLACNIC 673 100% 70
201.222.55.0/24 Valid RIR databaseLACNIC, RADB 673 100% 70
200.123.36.0/24 Valid RIR databaseLACNIC 663 99% 67
2803:c100::/32 Valid RIR databaseLACNIC, RADB 630 99% 67

AS-SET

AS28103's PeeringDB record names no AS-SET.

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: not announced10

Route objects not announced

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

131.161.252.0/22LACNIC, RADBValid
138.186.60.0/22LACNIC, RADBValid
179.189.218.0/23LACNIC, RADBValid
190.110.226.0/23LACNIC, RADBValid
190.110.230.0/23LACNICValid
190.110.246.0/23LACNICValid
190.211.240.0/22LACNIC, RADBValid
200.123.36.0/23LACNICValid
201.222.48.0/21LACNIC, RADBValid
201.222.48.0/22RADBValid

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.