bgpreport

Network · data from 2026-11-12

AS269078 SETEC.NET

Registry name: AS269078 - SETEC.NET SERVICOS DE INFORMATICA E COMUNICACAO LT, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269078, 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.179.124.0/23 No ROA Nonecovered by 45.179.124.0/22 669 99% 67
45.179.124.0/24 No ROA Nonecovered by 45.179.124.0/22 669 99% 67
45.179.126.0/24 No ROA Nonecovered by 45.179.126.0/23 665 99% 67
45.179.127.0/24 No ROA Nonecovered by 45.179.126.0/23 665 99% 67
45.179.125.0/24 No ROA Other IRR onlyRADB 672 100% 67
45.179.124.0/22 No ROA Other IRR onlyRADB, TC 665 99% 67
45.179.126.0/23 No ROA Other IRR onlyRADB 665 99% 67

AS-SET

AS269078'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 15 are in fix.csv.

  • ROA: none7
  • Route object: none4
  • Route object: RIR3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none45.179.124.0/23No ROA covers it. Add a ROA for AS269078, maxLength 23.669 of 673
Route object: none45.179.124.0/23No route object for it. A route object for 45.179.124.0/22 with origin AS269078 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269078 in the RIR database for the space.669 of 673
ROA: none45.179.124.0/24No ROA covers it. Add a ROA for AS269078, maxLength 24.669 of 673
Route object: none45.179.124.0/24No route object for it. A route object for 45.179.124.0/22 with origin AS269078 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269078 in the RIR database for the space.669 of 673
ROA: none45.179.126.0/24No ROA covers it. Add a ROA for AS269078, maxLength 24.665 of 673
Route object: none45.179.126.0/24No route object for it. A route object for 45.179.126.0/23 with origin AS269078 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269078 in the RIR database for the space.665 of 673
ROA: none45.179.127.0/24No ROA covers it. Add a ROA for AS269078, maxLength 24.665 of 673
Route object: none45.179.127.0/24No route object for it. A route object for 45.179.126.0/23 with origin AS269078 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269078 in the RIR database for the space.665 of 673
ROA: none45.179.125.0/24No ROA covers it. Add a ROA for AS269078, maxLength 24.672 of 673
Route object: RIR45.179.125.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.179.124.0/22No ROA covers it. Add a ROA for AS269078, maxLength 22.665 of 673
Route object: RIR45.179.124.0/22Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
ROA: none45.179.126.0/23No ROA covers it. Add a ROA for AS269078, maxLength 23.665 of 673
Route object: RIR45.179.126.0/23Route object only in RADB. Add it in the RIR database for the space.665 of 673

Route objects not announced

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

2804:5f20::/32RADB, TCNo 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.