bgpreport

Network · data from 2026-11-12

AS268093 AS268093 - DIRECTNET TELECOM LTDA

Registry name: AS268093 - DIRECTNET TELECOM LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268093, 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.169.28.0/24 No ROA Other IRR onlyRADB, TC 672 100% 66
45.169.30.0/24 No ROA Other IRR onlyRADB, TC 672 100% 66
45.169.31.0/24 No ROA Other IRR onlyRADB, TC 672 100% 66
45.169.29.0/24 No ROA Other IRR onlyRADB, TC 667 99% 66
2804:57e4::/34 No ROA Other IRR onlyRADB 635 100% 67
2804:57e4:4000::/34 No ROA Other IRR onlyRADB 635 100% 67
2804:57e4:c000::/34 No ROA Other IRR onlyRADB 635 100% 67
2804:57e4:8000::/34 No ROA Other IRR onlyRADB 632 99% 67
2804:57e4::/32 No ROA Other IRR onlyALTDB, RADB, TC 3 0%low visibility 3
45.169.28.0/23 No ROA Other IRR onlyRADB, TC 2 0%low visibility 2

AS-SET

AS268093 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 24 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none45.169.28.0/24No ROA covers it. Add a ROA for AS268093, maxLength 24.672 of 673
Route object: RIR45.169.28.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.169.30.0/24No ROA covers it. Add a ROA for AS268093, maxLength 24.672 of 673
Route object: RIR45.169.30.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.169.31.0/24No ROA covers it. Add a ROA for AS268093, maxLength 24.672 of 673
Route object: RIR45.169.31.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.169.29.0/24No ROA covers it. Add a ROA for AS268093, maxLength 24.667 of 673
Route object: RIR45.169.29.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none2804:57e4::/34No ROA covers it. Add a ROA for AS268093, maxLength 34.635 of 636
Route object: RIR2804:57e4::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:57e4:4000::/34No ROA covers it. Add a ROA for AS268093, maxLength 34.635 of 636
Route object: RIR2804:57e4:4000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:57e4:c000::/34No ROA covers it. Add a ROA for AS268093, maxLength 34.635 of 636
Route object: RIR2804:57e4:c000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:57e4:8000::/34No ROA covers it. Add a ROA for AS268093, maxLength 34.632 of 636
Route object: RIR2804:57e4:8000::/34Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none2804:57e4::/32No ROA covers it. Add a ROA for AS268093, maxLength 32.3 of 636
Route object: RIR2804:57e4::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.3 of 636
ROA: none45.169.28.0/23No ROA covers it. Add a ROA for AS268093, maxLength 23.2 of 673
Route object: RIR45.169.28.0/23Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

45.169.28.0/22ALTDB, RADB, TCNo ROA
45.169.30.0/23RADBNo ROA
2804:57e4:2000::/44RADBNo ROA
2804:57e4:2010::/44RADBNo 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.