bgpreport

Network · data from 2026-11-12

AS262417 UltraTelecom

Registry name: AS262417 - UltraTelecom Provedora de Internet, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262417, 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.255.132.0/23 Valid Nonecovered by 131.255.132.0/22 130 19% 42
131.255.134.0/23 Valid Nonecovered by 131.255.132.0/22 130 19% 42
168.195.228.0/23 Valid Nonecovered by 168.195.228.0/22 130 19% 42
168.195.230.0/23 Valid Nonecovered by 168.195.228.0/22 130 19% 42
177.200.128.0/23 Valid Nonecovered by 177.200.128.0/22 130 19% 42
177.200.130.0/23 Valid Nonecovered by 177.200.128.0/22 130 19% 42
2804:e24:fd80::/42 Valid Nonecovered by 2804:e24:8000::/33 4 1%low visibility 3
2804:e24:fd80::/43 Valid Nonecovered by 2804:e24:8000::/33 4 1%low visibility 3
2804:e24:fd80::/44 Valid Nonecovered by 2804:e24:8000::/33 4 1%low visibility 3
2804:e24:fd90::/44 Valid Nonecovered by 2804:e24:8000::/33 4 1%low visibility 3
2804:e24:fda0::/43 Valid Nonecovered by 2804:e24:8000::/33 4 1%low visibility 3
2804:e24:fda0::/44 Valid Nonecovered by 2804:e24:8000::/33 4 1%low visibility 3
2804:e24:fdb0::/44 Valid Nonecovered by 2804:e24:8000::/33 4 1%low visibility 3
2804:e24:fe80::/42 Valid Nonecovered by 2804:e24:8000::/33 4 1%low visibility 3
168.90.28.0/22 Valid Other IRR onlyALTDB, TC 672 100% 66
168.90.28.0/24 Valid Other IRR onlyALTDB 672 100% 66
168.195.228.0/22 Valid Other IRR onlyALTDB 672 100% 66
177.37.64.0/19 Valid Other IRR onlyTC 672 100% 66
177.37.84.0/22 Valid Other IRR onlyALTDB 672 100% 66
177.37.92.0/22 Valid Other IRR onlyALTDB 672 100% 66
177.129.200.0/22 Valid Other IRR onlyALTDB, TC 672 100% 66
177.200.128.0/22 Valid Other IRR onlyALTDB 672 100% 66
179.43.4.0/22 Valid Other IRR onlyALTDB, TC 672 100% 66
186.209.244.0/22 Valid Other IRR onlyTC 672 100% 66
186.209.248.0/21 Valid Other IRR onlyTC 672 100% 66
186.219.56.0/22 Valid Other IRR onlyTC 672 100% 66
131.255.132.0/22 Valid Other IRR onlyALTDB 670 100% 66
2804:e24::/32 Valid Other IRR onlyALTDB, RADB, TC 634 100% 69
2804:e24::/33 Valid Other IRR onlyTC 360 57% 64
2804:e24:8000::/33 Valid Other IRR onlyTC 360 57% 64
177.37.64.0/20 Valid Other IRR onlyALTDB, RADB, TC 214 32% 54
177.37.64.0/22 Valid Other IRR onlyALTDB 214 32% 54
177.37.64.0/23 Valid Other IRR onlyALTDB 214 32% 54
177.37.66.0/23 Valid Other IRR onlyALTDB 214 32% 54
177.37.68.0/22 Valid Other IRR onlyALTDB 214 32% 54
177.37.68.0/23 Valid Other IRR onlyALTDB 214 32% 54
177.37.72.0/22 Valid Other IRR onlyALTDB 214 32% 54
177.37.72.0/23 Valid Other IRR onlyALTDB 214 32% 54
177.37.74.0/23 Valid Other IRR onlyALTDB 214 32% 54
177.37.80.0/21 Valid Other IRR onlyALTDB, RADB, TC 214 32% 54
177.37.80.0/22 Valid Other IRR onlyALTDB 214 32% 54
177.37.82.0/23 Valid Other IRR onlyALTDB 214 32% 54
177.37.84.0/23 Valid Other IRR onlyALTDB 214 32% 54
177.37.88.0/21 Valid Other IRR onlyALTDB, RADB, TC 214 32% 54
177.37.88.0/22 Valid Other IRR onlyALTDB 214 32% 54
177.37.88.0/23 Valid Other IRR onlyALTDB 214 32% 54
177.37.90.0/23 Valid Other IRR onlyALTDB 214 32% 54
177.37.80.0/23 Valid Other IRR onlyALTDB 213 32% 54
177.37.86.0/23 Valid Other IRR onlyALTDB 213 32% 54
177.37.92.0/23 Valid Other IRR onlyALTDB 213 32% 54
177.37.94.0/23 Valid Other IRR onlyALTDB 213 32% 54
186.219.56.0/23 Valid Other IRR onlyTC 213 32% 54
186.219.58.0/23 Valid Other IRR onlyTC 213 32% 54
177.37.70.0/23 Valid Other IRR onlyALTDB 212 32% 54
179.63.176.0/23 Valid Other IRR onlyRADB 210 31% 54
168.90.28.0/23 Valid Other IRR onlyALTDB 209 31% 54
168.90.30.0/23 Valid Other IRR onlyALTDB 209 31% 54
177.37.76.0/22 Valid Other IRR onlyALTDB 209 31% 54
177.37.76.0/23 Valid Other IRR onlyTC 209 31% 54
177.37.78.0/23 Valid Other IRR onlyALTDB 209 31% 54
177.129.200.0/23 Valid Other IRR onlyALTDB 209 31% 54
177.129.202.0/23 Valid Other IRR onlyALTDB 209 31% 54
2804:e24:fe00::/42 Valid Other IRR onlyTC 4 1%low visibility 3
2804:e24:fff0::/48 Valid Other IRR onlyTC 4 1%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS262417: AS-ULTRATELECOM-BR. 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 (AS262417 isn't in the set, or no route object for AS262417 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 objectsAS262417 in itNot covered
AS-ULTRATELECOM-BR ALTDBlists itself further down2 member sets in no database: AS264262:AS-GLOBAL, AS266486:AS-GLOBAL 113181,993 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 168 are in fix.csv.

  • Route object: none14
  • Route object: RIR50
  • AS-SET: missing member2
  • Route object: not announced102
ChangePrefix or setDetailFull-table peers
Route object: none131.255.132.0/23No route object for it. A route object for 131.255.132.0/22 with origin AS262417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262417 in the RIR database for the space.130 of 673
Route object: none131.255.134.0/23No route object for it. A route object for 131.255.132.0/22 with origin AS262417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262417 in the RIR database for the space.130 of 673
Route object: none168.195.228.0/23No route object for it. A route object for 168.195.228.0/22 with origin AS262417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262417 in the RIR database for the space.130 of 673
Route object: none168.195.230.0/23No route object for it. A route object for 168.195.228.0/22 with origin AS262417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262417 in the RIR database for the space.130 of 673
Route object: none177.200.128.0/23No route object for it. A route object for 177.200.128.0/22 with origin AS262417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262417 in the RIR database for the space.130 of 673
Route object: none177.200.130.0/23No route object for it. A route object for 177.200.128.0/22 with origin AS262417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262417 in the RIR database for the space.130 of 673
Route object: none2804:e24:fd80::/42No route object for it. A route object for 2804:e24:8000::/33 with origin AS262417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262417 in the RIR database for the space.4 of 636
Route object: none2804:e24:fd80::/43No route object for it. A route object for 2804:e24:8000::/33 with origin AS262417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262417 in the RIR database for the space.4 of 636
Route object: none2804:e24:fd80::/44No route object for it. A route object for 2804:e24:8000::/33 with origin AS262417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262417 in the RIR database for the space.4 of 636
Route object: none2804:e24:fd90::/44No route object for it. A route object for 2804:e24:8000::/33 with origin AS262417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262417 in the RIR database for the space.4 of 636
Route object: none2804:e24:fda0::/43No route object for it. A route object for 2804:e24:8000::/33 with origin AS262417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262417 in the RIR database for the space.4 of 636
Route object: none2804:e24:fda0::/44No route object for it. A route object for 2804:e24:8000::/33 with origin AS262417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262417 in the RIR database for the space.4 of 636
Route object: none2804:e24:fdb0::/44No route object for it. A route object for 2804:e24:8000::/33 with origin AS262417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262417 in the RIR database for the space.4 of 636
Route object: none2804:e24:fe80::/42No route object for it. A route object for 2804:e24:8000::/33 with origin AS262417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262417 in the RIR database for the space.4 of 636
Route object: RIR168.90.28.0/22Route object only in ALTDB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.90.28.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.195.228.0/22Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.37.64.0/19Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.37.84.0/22Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.37.92.0/22Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.129.200.0/22Route object only in ALTDB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.200.128.0/22Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR179.43.4.0/22Route object only in ALTDB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.209.244.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.209.248.0/21Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.219.56.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR131.255.132.0/22Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:e24::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:e24::/33Route object only in TC. Add it in the RIR database for the space.360 of 636
Route object: RIR2804:e24:8000::/33Route object only in TC. Add it in the RIR database for the space.360 of 636
Route object: RIR177.37.64.0/20Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.64.0/22Route object only in ALTDB. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.64.0/23Route object only in ALTDB. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.66.0/23Route object only in ALTDB. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.68.0/22Route object only in ALTDB. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.68.0/23Route object only in ALTDB. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.72.0/22Route object only in ALTDB. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.72.0/23Route object only in ALTDB. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.74.0/23Route object only in ALTDB. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.80.0/21Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.80.0/22Route object only in ALTDB. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.82.0/23Route object only in ALTDB. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.84.0/23Route object only in ALTDB. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.88.0/21Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.88.0/22Route object only in ALTDB. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.88.0/23Route object only in ALTDB. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.90.0/23Route object only in ALTDB. Add it in the RIR database for the space.214 of 673
Route object: RIR177.37.80.0/23Route object only in ALTDB. Add it in the RIR database for the space.213 of 673
Route object: RIR177.37.86.0/23Route object only in ALTDB. Add it in the RIR database for the space.213 of 673
Route object: RIR177.37.92.0/23Route object only in ALTDB. Add it in the RIR database for the space.213 of 673
Route object: RIR177.37.94.0/23Route object only in ALTDB. Add it in the RIR database for the space.213 of 673
Route object: RIR186.219.56.0/23Route object only in TC. Add it in the RIR database for the space.213 of 673
Route object: RIR186.219.58.0/23Route object only in TC. Add it in the RIR database for the space.213 of 673
Route object: RIR177.37.70.0/23Route object only in ALTDB. Add it in the RIR database for the space.212 of 673
Route object: RIR179.63.176.0/23Route object only in RADB. Add it in the RIR database for the space.210 of 673
Route object: RIR168.90.28.0/23Route object only in ALTDB. Add it in the RIR database for the space.209 of 673
Route object: RIR168.90.30.0/23Route object only in ALTDB. Add it in the RIR database for the space.209 of 673
Route object: RIR177.37.76.0/22Route object only in ALTDB. Add it in the RIR database for the space.209 of 673
Route object: RIR177.37.76.0/23Route object only in TC. Add it in the RIR database for the space.209 of 673
Route object: RIR177.37.78.0/23Route object only in ALTDB. Add it in the RIR database for the space.209 of 673
Route object: RIR177.129.200.0/23Route object only in ALTDB. Add it in the RIR database for the space.209 of 673
Route object: RIR177.129.202.0/23Route object only in ALTDB. Add it in the RIR database for the space.209 of 673
Route object: RIR2804:e24:fe00::/42Route object only in TC. Add it in the RIR database for the space.4 of 636
Route object: RIR2804:e24:fff0::/48Route object only in TC. Add it in the RIR database for the space.4 of 636
AS-SET: missing memberAS-ULTRATELECOM-BRAS-ULTRATELECOM-BR (ALTDB) lists AS264262:AS-GLOBAL; no IRR database read has it.
AS-SET: missing memberAS-ULTRATELECOM-BRAS-ULTRATELECOM-BR (ALTDB) lists AS266486:AS-GLOBAL; no IRR database read has it.

Route objects not announced

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

45.164.206.0/24RADBValid
168.90.29.0/24ALTDBValid
168.90.30.0/24ALTDBValid
168.90.31.0/24ALTDBValid
177.37.64.0/21ALTDBValid
177.37.64.0/24ALTDBValid
177.37.65.0/24ALTDBValid
177.37.66.0/24ALTDBValid
177.37.67.0/24ALTDBValid
177.37.68.0/24ALTDBValid
177.37.69.0/24ALTDBValid
177.37.70.0/24ALTDBValid
177.37.71.0/24ALTDBValid
177.37.72.0/21ALTDBValid
177.37.72.0/24ALTDBValid
177.37.73.0/24ALTDBValid
177.37.74.0/24ALTDBValid
177.37.75.0/24ALTDBValid
177.37.76.0/24ALTDBValid
177.37.77.0/24ALTDBValid
177.37.78.0/24ALTDBValid
177.37.79.0/24ALTDBValid
177.37.80.0/20NTTCOMValid
177.37.80.0/24ALTDBValid
177.37.81.0/24ALTDBValid
177.37.82.0/24ALTDBValid
177.37.83.0/24ALTDBValid
177.37.84.0/24ALTDBValid
177.37.85.0/24ALTDBValid
177.37.86.0/24ALTDBValid
177.37.87.0/24ALTDBValid
177.37.88.0/24ALTDBValid
177.37.89.0/24ALTDBValid
177.37.90.0/24ALTDBValid
177.37.91.0/24ALTDBValid
177.37.92.0/24ALTDBValid
177.37.93.0/24ALTDBValid
177.37.94.0/24ALTDBValid
177.37.95.0/24ALTDBValid
177.125.181.0/24RADBValid
177.129.200.0/24ALTDBValid
177.129.201.0/24ALTDBValid
177.129.202.0/24ALTDBValid
177.129.203.0/24ALTDBValid
179.43.4.0/23ALTDBValid
179.43.4.0/24ALTDBValid
179.43.5.0/24ALTDBValid
179.43.6.0/23ALTDBValid
179.43.6.0/24ALTDBValid
179.43.7.0/24ALTDBValid
186.209.244.0/23TCValid
186.209.244.0/24TCValid
186.209.245.0/24TCValid
186.209.246.0/23TCValid
186.209.246.0/24TCValid
186.209.247.0/24TCValid
186.209.248.0/22TCValid
186.209.248.0/23TCValid
186.209.248.0/24TCValid
186.209.249.0/24TCValid
186.209.250.0/23TCValid
186.209.250.0/24TCValid
186.209.251.0/24TCValid
186.209.252.0/22TCValid
186.209.252.0/23TCValid
186.209.252.0/24TCValid
186.209.253.0/24TCValid
186.209.254.0/23TCValid
186.209.254.0/24TCValid
186.209.255.0/24TCValid
186.219.56.0/24TCValid
186.219.57.0/24TCValid
186.219.58.0/24RADB, TCValid
186.219.59.0/24TCValid
2804:e24:3020::/48TCValid
2804:e24:4000::/40TCValid
2804:e24:fd00::/42TCValid
2804:e24:fd00::/43TCValid
2804:e24:fd00::/44TCValid
2804:e24:fd10::/44TCValid
2804:e24:fd20::/43TCValid
2804:e24:fd20::/44TCValid
2804:e24:fd30::/44TCValid
2804:e24:fd40::/42TCValid
2804:e24:fd40::/43TCValid
2804:e24:fd40::/44TCValid
2804:e24:fd50::/44TCValid
2804:e24:fd60::/43TCValid
2804:e24:fd60::/44TCValid
2804:e24:fd70::/44TCValid
2804:e24:fe40::/42ALTDB, TCValid
2804:e24:fe40::/43TCValid
2804:e24:fe40::/44TCValid
2804:e24:fe50::/44TCValid
2804:e24:fe60::/43TCValid
2804:e24:fe60::/44TCValid
2804:e24:fe70::/44TCValid
2804:e24:fec0::/42ALTDBValid
2804:e24:fff1::/48ALTDB, TCValid
2804:e24:fff2::/48ALTDB, TCValid
2804:e24:fff3::/48TCValid
2804:e24:fffa::/48TCValid

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.