bgpreport

Network · data from 2026-11-12

AS37575 UNITEL T Telecomunicacoes, Sociedade Unipessoal S.A.

Registry name: UNITEL T+ Telecomunicacoes, Sociedade Unipessoal, S.A. - UNITEL T+ Telecomunicacoes, Sociedade Unipessoal, S.A., CV · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37575, 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.
102.212.175.0/24 No ROA Other origin only 666 99% 67
2c0f:f498::/32 No ROA RIR databaseAFRINIC 635 100% 69
38.41.80.0/22 Valid Nonecovered by 38.41.80.0/21 670 100% 68
38.41.84.0/22 Valid Nonecovered by 38.41.80.0/21 670 100% 68
38.71.126.0/23 Valid Nonecovered by 38.71.124.0/22 670 100% 68
38.71.124.0/23 Valid Nonecovered by 38.71.124.0/22 667 99% 68
38.41.80.0/21 Valid RIR databaseARIN 670 100% 68
38.71.124.0/22 Valid RIR databaseARIN 670 100% 68
41.79.124.0/22 Valid RIR databaseAFRINIC 670 100% 68
169.239.12.0/22 Valid RIR databaseAFRINIC 670 100% 68
102.222.140.0/22 Valid RIR databaseAFRINIC 667 99% 68

AS-SET

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

  • ROA: none2
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none102.212.175.0/24No ROA covers it. Add a ROA for AS37575, maxLength 24.666 of 673
Route object: none102.212.175.0/24Route objects for it name AS329245. Add a route object with origin AS37575 in the RIR database for the space.666 of 673
ROA: none2c0f:f498::/32No ROA covers it. Add a ROA for AS37575, maxLength 32.635 of 636
Route object: none38.41.80.0/22No route object for it. A route object for 38.41.80.0/21 with origin AS37575 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37575 in the RIR database for the space.670 of 673
Route object: none38.41.84.0/22No route object for it. A route object for 38.41.80.0/21 with origin AS37575 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37575 in the RIR database for the space.670 of 673
Route object: none38.71.126.0/23No route object for it. A route object for 38.71.124.0/22 with origin AS37575 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37575 in the RIR database for the space.670 of 673
Route object: none38.71.124.0/23No route object for it. A route object for 38.71.124.0/22 with origin AS37575 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37575 in the RIR database for the space.667 of 673

Route objects not announced

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