bgpreport

Network · data from 2026-11-12

AS262706 Ultranet Telecomunicações

Registry name: AS262706 - Ultranet Telecomunicacoes Ltda, BR · PeeringDB

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

Announced routes

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

207.153.110.0/24 No ROA Other origin only 673 100% 67
2804:12d0::/36 Valid Nonecovered by 2804:12d0::/32 635 100% 69
187.109.44.0/23 Valid Other IRR onlyTC 673 100% 67
187.109.36.0/22 Valid Other IRR onlyTC 671 100% 67
187.109.40.0/22 Valid Other IRR onlyTC 671 100% 67
187.109.32.0/23 Valid Other IRR onlyTC 669 99% 67
187.109.34.0/23 Valid Other IRR onlyTC 668 99% 67
187.109.46.0/24 Valid Other IRR onlyTC 668 99% 67
187.109.47.0/24 Valid Other IRR onlyTC 668 99% 67
187.109.34.0/24 Valid Other IRR onlyTC 663 99% 67
2804:12d0::/32 Valid Other IRR onlyRADB, TC 635 100% 69
187.109.33.0/24 Valid Other IRR onlyTC 208 31% 56
187.109.36.0/24 Valid Other IRR onlyTC 208 31% 56
187.109.37.0/24 Valid Other IRR onlyTC 208 31% 56
187.109.38.0/24 Valid Other IRR onlyTC 208 31% 56
187.109.39.0/24 Valid Other IRR onlyTC 208 31% 56
187.109.41.0/24 Valid Other IRR onlyTC 208 31% 56
187.109.42.0/24 Valid Other IRR onlyTC 208 31% 56
187.109.43.0/24 Valid Other IRR onlyTC 208 31% 56
187.109.40.0/24 Valid Other IRR onlyTC 207 31% 56
187.109.35.0/24 Valid Other IRR onlyTC 136 20% 45

AS-SET

AS262706'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 30 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR19
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none207.153.110.0/24No ROA covers it. Add a ROA for AS262706, maxLength 24.673 of 673
Route object: none207.153.110.0/24Route objects for it name AS20406. Add a route object with origin AS262706 in the RIR database for the space.673 of 673
Route object: none2804:12d0::/36No route object for it. A route object for 2804:12d0::/32 with origin AS262706 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262706 in the RIR database for the space.635 of 636
Route object: RIR187.109.44.0/23Route object only in TC. Add it in the RIR database for the space.673 of 673
Route object: RIR187.109.36.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.40.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.32.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR187.109.34.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR187.109.46.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR187.109.47.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR187.109.34.0/24Route object only in TC. Add it in the RIR database for the space.663 of 673
Route object: RIR2804:12d0::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR187.109.33.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.109.36.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.109.37.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.109.38.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.109.39.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.109.41.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.109.42.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.109.43.0/24Route object only in TC. Add it in the RIR database for the space.208 of 673
Route object: RIR187.109.40.0/24Route object only in TC. Add it in the RIR database for the space.207 of 673
Route object: RIR187.109.35.0/24Route object only in TC. Add it in the RIR database for the space.136 of 673

Route objects not announced

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

168.194.68.0/22RADBNo ROA
168.194.68.0/23RADBNo ROA
179.96.208.0/21RADBNo ROA
187.109.32.0/20ALTDB, RADB, TCNo ROA
191.6.240.0/21RADBNo ROA
191.242.32.0/20RADBNo ROA
191.243.80.0/21ALTDB, RADB, TCNo ROA
204.16.0.0/21RADBNo ROA

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.