bgpreport

Network · data from 2026-11-12

AS28080 Interredes

Registry name: AS28080 - Interredes S.A., AR · PeeringDB

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

Announced routes

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

143.0.169.0/24 Valid Nonecovered by 143.0.168.0/22 670 100% 67
143.0.170.0/24 Valid Nonecovered by 143.0.168.0/22 670 100% 67
143.0.171.0/24 Valid Nonecovered by 143.0.168.0/22 670 100% 67
200.114.99.0/24 Valid Nonecovered by 200.114.96.0/21 670 100% 67
200.114.100.0/24 Valid Nonecovered by 200.114.96.0/21 670 100% 67
200.114.101.0/24 Valid Nonecovered by 200.114.96.0/21 670 100% 67
143.0.168.0/24 Valid Nonecovered by 143.0.168.0/22 669 99% 67
200.114.96.0/23 Valid Nonecovered by 200.114.96.0/21 669 99% 67
200.114.96.0/24 Valid Nonecovered by 200.114.96.0/21 669 99% 67
200.114.97.0/24 Valid Nonecovered by 200.114.96.0/21 669 99% 67
200.114.98.0/24 Valid Nonecovered by 200.114.96.0/21 669 99% 67
200.114.102.0/23 Valid Nonecovered by 200.114.96.0/21 669 99% 67
200.114.102.0/24 Valid Nonecovered by 200.114.96.0/21 669 99% 67
200.114.103.0/24 Valid Nonecovered by 200.114.96.0/21 669 99% 67
143.0.168.0/22 Valid RIR databaseLACNIC 670 100% 67
2803:be40::/32 Valid RIR databaseLACNIC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS28080: AS28080:AS-IRR. 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 (AS28080 isn't in the set, or no route object for AS28080 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 objectsAS28080 in itNot covered
AS28080:AS-IRR LACNIC 110 No 16

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

  • Route object: none14
  • AS-SET: own ASN1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none143.0.169.0/24No route object for it. A route object for 143.0.168.0/22 with origin AS28080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28080 in the RIR database for the space.670 of 673
Route object: none143.0.170.0/24No route object for it. A route object for 143.0.168.0/22 with origin AS28080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28080 in the RIR database for the space.670 of 673
Route object: none143.0.171.0/24No route object for it. A route object for 143.0.168.0/22 with origin AS28080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28080 in the RIR database for the space.670 of 673
Route object: none200.114.99.0/24No route object for it. A route object for 200.114.96.0/21 with origin AS28080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28080 in the RIR database for the space.670 of 673
Route object: none200.114.100.0/24No route object for it. A route object for 200.114.96.0/21 with origin AS28080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28080 in the RIR database for the space.670 of 673
Route object: none200.114.101.0/24No route object for it. A route object for 200.114.96.0/21 with origin AS28080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28080 in the RIR database for the space.670 of 673
Route object: none143.0.168.0/24No route object for it. A route object for 143.0.168.0/22 with origin AS28080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28080 in the RIR database for the space.669 of 673
Route object: none200.114.96.0/23No route object for it. A route object for 200.114.96.0/21 with origin AS28080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28080 in the RIR database for the space.669 of 673
Route object: none200.114.96.0/24No route object for it. A route object for 200.114.96.0/21 with origin AS28080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28080 in the RIR database for the space.669 of 673
Route object: none200.114.97.0/24No route object for it. A route object for 200.114.96.0/21 with origin AS28080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28080 in the RIR database for the space.669 of 673
Route object: none200.114.98.0/24No route object for it. A route object for 200.114.96.0/21 with origin AS28080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28080 in the RIR database for the space.669 of 673
Route object: none200.114.102.0/23No route object for it. A route object for 200.114.96.0/21 with origin AS28080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28080 in the RIR database for the space.669 of 673
Route object: none200.114.102.0/24No route object for it. A route object for 200.114.96.0/21 with origin AS28080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28080 in the RIR database for the space.669 of 673
Route object: none200.114.103.0/24No route object for it. A route object for 200.114.96.0/21 with origin AS28080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28080 in the RIR database for the space.669 of 673
AS-SET: own ASNAS28080:AS-IRRAS28080 isn't in AS28080:AS-IRR (LACNIC) once expanded. Add AS28080 to it.

Route objects not announced

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

200.114.96.0/21LACNICValid

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.