bgpreport

Network · data from 2026-11-12

AS265290 Uplink Brasil

Registry name: AS265290 - Uplink Telecom, BR · PeeringDB

15IPv4 routes 46.7% RPKI valid · 60.0% with a route object
8IPv6 routes 100.0% RPKI valid · 62.5% with a route object
0RPKI invalid 0 origin · 0 maxLength
8No ROA 9 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS265290, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265290, 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.71.62.0/24 No ROA Other origin onlycovered by 177.71.60.0/22 671 100% 67
45.179.5.0/24 No ROA None 667 99% 67
187.86.8.0/24 No ROA Other origin only 592 88% 65
187.86.11.0/24 No ROA Other origin only 592 88% 65
187.86.9.0/24 No ROA Other origin only 557 83% 66
187.86.10.0/24 No ROA Other origin only 231 34% 54
177.71.60.0/22 No ROA Other IRR onlyRADB 671 100% 67
45.179.4.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
2804:2d94::/33 Valid Nonecovered by 2804:2d94::/32 629 99% 67
2804:2d94:8000::/33 Valid Nonecovered by 2804:2d94::/32 629 99% 67
2804:2d94:fa00::/40 Valid Nonecovered by 2804:2d94:c000::/34 6 1%low visibility 6
168.90.204.0/22 Valid Other IRR onlyALTDB, RADB, TC 672 100% 67
168.90.206.0/24 Valid Other IRR onlyRADB 670 100% 66
168.90.207.0/24 Valid Other IRR onlyRADB 670 100% 66
168.90.204.0/23 Valid Other IRR onlyALTDB, RADB 668 99% 67
168.90.206.0/23 Valid Other IRR onlyALTDB, RADB 668 99% 67
168.90.204.0/24 Valid Other IRR onlyRADB 666 99% 67
168.90.205.0/24 Valid Other IRR onlyRADB 666 99% 67
2804:2d94::/32 Valid Other IRR onlyALTDB, RADB, TC 630 99% 67
2804:2d94::/34 Valid Other IRR onlyALTDB, RADB 6 1%low visibility 6
2804:2d94:4000::/34 Valid Other IRR onlyALTDB, RADB 6 1%low visibility 6
2804:2d94:8000::/34 Valid Other IRR onlyALTDB, RADB 6 1%low visibility 6
2804:2d94:c000::/34 Valid Other IRR onlyALTDB, RADB 6 1%low visibility 6

AS-SET

PeeringDB's irr_as_set for AS265290: AS265290. 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 (AS265290 isn't in the set, or no route object for AS265290 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 objectsAS265290 in itNot covered
AS265290 A single AS number, not a set: AS265290 (this network), 14 route objects.

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

  • ROA: none8
  • Route object: none9
  • Route object: RIR14
ChangePrefix or setDetailFull-table peers
ROA: none177.71.62.0/24No ROA covers it. Add a ROA for AS265290, maxLength 24.671 of 673
Route object: none177.71.62.0/24Route objects for it name AS262560. A route object for 177.71.60.0/22 with origin AS265290 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265290 in the RIR database for the space.671 of 673
ROA: none45.179.5.0/24No ROA covers it. Add a ROA for AS265290, maxLength 24.667 of 673
Route object: none45.179.5.0/24No route object for it. Add a route object with origin AS265290 in the RIR database for the space.667 of 673
ROA: none187.86.8.0/24No ROA covers it. Add a ROA for AS265290, maxLength 24.592 of 673
Route object: none187.86.8.0/24Route objects for it name AS28135. Add a route object with origin AS265290 in the RIR database for the space.592 of 673
ROA: none187.86.11.0/24No ROA covers it. Add a ROA for AS265290, maxLength 24.592 of 673
Route object: none187.86.11.0/24Route objects for it name AS28135. Add a route object with origin AS265290 in the RIR database for the space.592 of 673
ROA: none187.86.9.0/24No ROA covers it. Add a ROA for AS265290, maxLength 24.557 of 673
Route object: none187.86.9.0/24Route objects for it name AS28135. Add a route object with origin AS265290 in the RIR database for the space.557 of 673
ROA: none187.86.10.0/24No ROA covers it. Add a ROA for AS265290, maxLength 24.231 of 673
Route object: none187.86.10.0/24Route objects for it name AS28135. Add a route object with origin AS265290 in the RIR database for the space.231 of 673
ROA: none177.71.60.0/22No ROA covers it. Add a ROA for AS265290, maxLength 22.671 of 673
Route object: RIR177.71.60.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.179.4.0/24No ROA covers it. Add a ROA for AS265290, maxLength 24.2 of 673
Route object: RIR45.179.4.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: none2804:2d94::/33No route object for it. A route object for 2804:2d94::/32 with origin AS265290 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265290 in the RIR database for the space.629 of 636
Route object: none2804:2d94:8000::/33No route object for it. A route object for 2804:2d94::/32 with origin AS265290 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265290 in the RIR database for the space.629 of 636
Route object: none2804:2d94:fa00::/40No route object for it. A route object for 2804:2d94:c000::/34 with origin AS265290 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265290 in the RIR database for the space.6 of 636
Route object: RIR168.90.204.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.90.206.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR168.90.207.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR168.90.204.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR168.90.206.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR168.90.204.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR168.90.205.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:2d94::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:2d94::/34Route object only in ALTDB, RADB. Add it in the RIR database for the space.6 of 636
Route object: RIR2804:2d94:4000::/34Route object only in ALTDB, RADB. Add it in the RIR database for the space.6 of 636
Route object: RIR2804:2d94:8000::/34Route object only in ALTDB, RADB. Add it in the RIR database for the space.6 of 636
Route object: RIR2804:2d94:c000::/34Route object only in ALTDB, RADB. Add it in the RIR database for the space.6 of 636

Route objects not announced

Every route object with origin AS265290 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.