bgpreport

Network · data from 2026-11-12

AS262324 Brasil TecPar (Allrede/Unilink)

Registry name: AS262324 - ALLREDE TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262324, 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.
177.67.28.0/24 Valid Nonecovered by 177.67.28.0/22 669 99% 67
177.67.29.0/24 Valid Nonecovered by 177.67.28.0/22 669 99% 67
177.67.30.0/24 Valid Nonecovered by 177.67.28.0/22 669 99% 67
177.67.31.0/24 Valid Nonecovered by 177.67.28.0/22 669 99% 67
177.124.136.0/24 Valid Nonecovered by 177.124.136.0/22 669 99% 67
177.124.137.0/24 Valid Nonecovered by 177.124.136.0/22 669 99% 67
177.124.138.0/24 Valid Nonecovered by 177.124.136.0/22 669 99% 67
177.124.139.0/24 Valid Nonecovered by 177.124.136.0/22 669 99% 67
177.67.28.0/22 Valid Other IRR onlyALTDB, RADB, TC 669 99% 67
177.124.136.0/22 Valid Other IRR onlyALTDB, RADB, TC 669 99% 67
143.202.128.0/22 Valid Other IRR onlyALTDB, RADB, TC 668 99% 67
2804:7d0::/32 Valid Other IRR onlyALTDB, RADB, TC 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS262324: AS262324:AS-ALLREDE-UNILINK. 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 (AS262324 isn't in the set, or no route object for AS262324 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 objectsAS262324 in itNot covered
AS262324:AS-ALLREDE-UNILINK TC 134 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 12 are in fix.csv.

  • Route object: none8
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none177.67.28.0/24No route object for it. A route object for 177.67.28.0/22 with origin AS262324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262324 in the RIR database for the space.669 of 673
Route object: none177.67.29.0/24No route object for it. A route object for 177.67.28.0/22 with origin AS262324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262324 in the RIR database for the space.669 of 673
Route object: none177.67.30.0/24No route object for it. A route object for 177.67.28.0/22 with origin AS262324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262324 in the RIR database for the space.669 of 673
Route object: none177.67.31.0/24No route object for it. A route object for 177.67.28.0/22 with origin AS262324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262324 in the RIR database for the space.669 of 673
Route object: none177.124.136.0/24No route object for it. A route object for 177.124.136.0/22 with origin AS262324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262324 in the RIR database for the space.669 of 673
Route object: none177.124.137.0/24No route object for it. A route object for 177.124.136.0/22 with origin AS262324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262324 in the RIR database for the space.669 of 673
Route object: none177.124.138.0/24No route object for it. A route object for 177.124.136.0/22 with origin AS262324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262324 in the RIR database for the space.669 of 673
Route object: none177.124.139.0/24No route object for it. A route object for 177.124.136.0/22 with origin AS262324 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262324 in the RIR database for the space.669 of 673
Route object: RIR177.67.28.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.124.136.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR143.202.128.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:7d0::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS262324 is announced.

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.