bgpreport

Network · data from 2026-11-12

AS272750 AS272750 - SB CONECT LTDA

Registry name: AS272750 - SB CONECT LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272750, 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.
187.49.148.0/23 No ROA Other origin onlycovered by 187.49.148.0/22 672 100% 67
187.49.150.0/23 No ROA Other origin onlycovered by 187.49.148.0/22 672 100% 67
187.49.151.0/24 No ROA Other origin onlycovered by 187.49.148.0/22 670 100% 67
187.49.150.0/24 No ROA Other origin onlycovered by 187.49.148.0/22 667 99% 67
187.49.148.0/22 No ROA Other IRR onlyTC 672 100% 67
2804:8814::/32 No ROA Other IRR onlyRADB, TC 633 100% 67

AS-SET

AS272750 isn't in PeeringDB, where networks name their 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none187.49.148.0/23No ROA covers it. Add a ROA for AS272750, maxLength 23.672 of 673
Route object: none187.49.148.0/23Route objects for it name AS270532. A route object for 187.49.148.0/22 with origin AS272750 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272750 in the RIR database for the space.672 of 673
ROA: none187.49.150.0/23No ROA covers it. Add a ROA for AS272750, maxLength 23.672 of 673
Route object: none187.49.150.0/23Route objects for it name AS270532. A route object for 187.49.148.0/22 with origin AS272750 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272750 in the RIR database for the space.672 of 673
ROA: none187.49.151.0/24No ROA covers it. Add a ROA for AS272750, maxLength 24.670 of 673
Route object: none187.49.151.0/24Route objects for it name AS270532. A route object for 187.49.148.0/22 with origin AS272750 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272750 in the RIR database for the space.670 of 673
ROA: none187.49.150.0/24No ROA covers it. Add a ROA for AS272750, maxLength 24.667 of 673
Route object: none187.49.150.0/24Route objects for it name AS270532. A route object for 187.49.148.0/22 with origin AS272750 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272750 in the RIR database for the space.667 of 673
ROA: none187.49.148.0/22No ROA covers it. Add a ROA for AS272750, maxLength 22.672 of 673
Route object: RIR187.49.148.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:8814::/32No ROA covers it. Add a ROA for AS272750, maxLength 32.633 of 636
Route object: RIR2804:8814::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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