bgpreport

Network · data from 2026-11-12

AS268482 Connect Telecomunicações

Registry name: AS268482 - Connect Telecomunicacoes LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268482, 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.
45.239.244.0/22 Valid Other IRR onlyALTDB, RADB, TC 669 99% 68
2804:51e0::/32 Valid Other IRR onlyALTDB, RADB, TC 635 100% 69
45.239.244.0/23 Valid Other IRR onlyRADB, TC 7 1%low visibility 5
45.239.246.0/23 Valid Other IRR onlyRADB, TC 7 1%low visibility 5
2804:51e0::/33 Valid Other IRR onlyRADB, TC 6 1%low visibility 5
2804:51e0:8000::/33 Valid Other IRR onlyRADB, TC 6 1%low visibility 5

AS-SET

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

  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: RIR45.239.244.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:51e0::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR45.239.244.0/23Route object only in RADB, TC. Add it in the RIR database for the space.7 of 673
Route object: RIR45.239.246.0/23Route object only in RADB, TC. Add it in the RIR database for the space.7 of 673
Route object: RIR2804:51e0::/33Route object only in RADB, TC. Add it in the RIR database for the space.6 of 636
Route object: RIR2804:51e0:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.6 of 636

Route objects not announced

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