bgpreport

Network · data from 2026-11-12

AS266325 SOURCE CONNECT TELECOMUNICAÇÕES

Registry name: AS266325 - SOURCE CONNECT TELECOMUNICACOES EIRELI ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266325, 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.
170.238.99.0/24 No ROA Nonecovered by 170.238.96.0/22 672 100% 66
170.238.96.0/23 No ROA Nonecovered by 170.238.96.0/22 670 100% 66
170.238.98.0/24 No ROA Nonecovered by 170.238.96.0/22 670 100% 66
2804:3614:1000::/48 No ROA Nonecovered by 2804:3614::/32 635 100% 67
2804:3614:8000::/45 No ROA Nonecovered by 2804:3614::/32 635 100% 67
2804:3614::/32 No ROA Other IRR onlyRADB 634 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none5
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none170.238.99.0/24No ROA covers it. Add a ROA for AS266325, maxLength 24.672 of 673
Route object: none170.238.99.0/24No route object for it. A route object for 170.238.96.0/22 with origin AS266325 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266325 in the RIR database for the space.672 of 673
ROA: none170.238.96.0/23No ROA covers it. Add a ROA for AS266325, maxLength 23.670 of 673
Route object: none170.238.96.0/23No route object for it. A route object for 170.238.96.0/22 with origin AS266325 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266325 in the RIR database for the space.670 of 673
ROA: none170.238.98.0/24No ROA covers it. Add a ROA for AS266325, maxLength 24.670 of 673
Route object: none170.238.98.0/24No route object for it. A route object for 170.238.96.0/22 with origin AS266325 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266325 in the RIR database for the space.670 of 673
ROA: none2804:3614:1000::/48No ROA covers it. Add a ROA for AS266325, maxLength 48.635 of 636
Route object: none2804:3614:1000::/48No route object for it. A route object for 2804:3614::/32 with origin AS266325 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266325 in the RIR database for the space.635 of 636
ROA: none2804:3614:8000::/45No ROA covers it. Add a ROA for AS266325, maxLength 45.635 of 636
Route object: none2804:3614:8000::/45No route object for it. A route object for 2804:3614::/32 with origin AS266325 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266325 in the RIR database for the space.635 of 636
ROA: none2804:3614::/32No ROA covers it. Add a ROA for AS266325, maxLength 32.634 of 636
Route object: RIR2804:3614::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

170.238.96.0/22RADBNo ROA

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.