bgpreport

Network · data from 2026-11-12

AS268939 AS268939 - CIDADE SONHO TELECOM EIRELI - EPP

Registry name: AS268939 - CIDADE SONHO TELECOM EIRELI - EPP, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268939, 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.
2804:5cec::/33 Valid Nonecovered by 2804:5cec::/32 17 3%low visibility 8
2804:5cec:8000::/33 Valid Nonecovered by 2804:5cec::/32 17 3%low visibility 8
45.176.24.0/23 Valid Nonecovered by 45.176.24.0/22 12 2%low visibility 6
45.176.26.0/23 Valid Nonecovered by 45.176.24.0/22 12 2%low visibility 6
45.176.24.0/22 Valid Other IRR onlyRADB 669 99% 67
2804:5cec::/32 Valid Other IRR onlyRADB 633 100% 70

AS-SET

AS268939 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 10 are in fix.csv.

  • Route object: none4
  • Route object: RIR2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2804:5cec::/33No route object for it. A route object for 2804:5cec::/32 with origin AS268939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268939 in the RIR database for the space.17 of 636
Route object: none2804:5cec:8000::/33No route object for it. A route object for 2804:5cec::/32 with origin AS268939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268939 in the RIR database for the space.17 of 636
Route object: none45.176.24.0/23No route object for it. A route object for 45.176.24.0/22 with origin AS268939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268939 in the RIR database for the space.12 of 673
Route object: none45.176.26.0/23No route object for it. A route object for 45.176.24.0/22 with origin AS268939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268939 in the RIR database for the space.12 of 673
Route object: RIR45.176.24.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:5cec::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

45.176.24.0/24RADBValid
45.176.25.0/24RADBValid
45.176.26.0/24RADBValid
45.176.27.0/24RADBValid

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.