bgpreport

Network · data from 2026-11-12

AS266348 S. C. SERVICOS E REDES LTDA - ME

Registry name: AS266348 - REDE UNICON, BR · PeeringDB

6IPv4 routes 100.0% RPKI valid · 50.0% with a route object
3IPv6 routes 100.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS266348, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266348, 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:3670::/33 Valid Nonecovered by 2804:3670::/32 634 100% 67
2804:3670:8000::/33 Valid Nonecovered by 2804:3670::/32 634 100% 67
170.239.108.0/24 Valid Nonecovered by 170.239.108.0/23 133 20% 45
170.239.109.0/24 Valid Nonecovered by 170.239.108.0/23 133 20% 45
170.239.110.0/24 Valid Nonecovered by 170.239.110.0/23 133 20% 45
170.239.108.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
170.239.108.0/23 Valid Other IRR onlyRADB 671 100% 66
170.239.110.0/23 Valid Other IRR onlyRADB 671 100% 66
2804:3670::/32 Valid Other IRR onlyRADB, TC 635 100% 69

AS-SET

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

  • Route object: none5
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none2804:3670::/33No route object for it. A route object for 2804:3670::/32 with origin AS266348 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266348 in the RIR database for the space.634 of 636
Route object: none2804:3670:8000::/33No route object for it. A route object for 2804:3670::/32 with origin AS266348 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266348 in the RIR database for the space.634 of 636
Route object: none170.239.108.0/24No route object for it. A route object for 170.239.108.0/23 with origin AS266348 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266348 in the RIR database for the space.133 of 673
Route object: none170.239.109.0/24No route object for it. A route object for 170.239.108.0/23 with origin AS266348 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266348 in the RIR database for the space.133 of 673
Route object: none170.239.110.0/24No route object for it. A route object for 170.239.110.0/23 with origin AS266348 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266348 in the RIR database for the space.133 of 673
Route object: RIR170.239.108.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.239.108.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR170.239.110.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:3670::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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