bgpreport

Network · data from 2026-11-12

AS268335 ORACLON TELECOM

Registry name: AS268335 - ORACLON TELECOM, BR · PeeringDB

8IPv4 routes 87.5% RPKI valid · 25.0% with a route object
8IPv6 routes 100.0% RPKI valid · 12.5% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 13 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS268335, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268335, 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.

38.211.113.0/24 No ROA Other IRR onlyNTTCOM, RADB 669 99% 67
45.238.100.0/23 Valid Nonecovered by 45.238.100.0/22 671 100% 67
45.238.102.0/23 Valid Nonecovered by 45.238.100.0/22 671 100% 67
45.238.100.0/24 Valid Nonecovered by 45.238.100.0/22 669 99% 67
45.238.101.0/24 Valid Nonecovered by 45.238.100.0/22 669 99% 67
45.238.102.0/24 Valid Nonecovered by 45.238.100.0/22 669 99% 67
45.238.103.0/24 Valid Nonecovered by 45.238.100.0/22 669 99% 67
2804:4f90::/34 Valid Nonecovered by 2804:4f90::/32 634 100% 67
2804:4f90:200::/40 Valid Nonecovered by 2804:4f90::/32 634 100% 67
2804:4f90:200::/41 Valid Nonecovered by 2804:4f90::/32 634 100% 67
2804:4f90:4000::/34 Valid Nonecovered by 2804:4f90::/32 634 100% 67
2804:4f90:4001::/48 Valid Nonecovered by 2804:4f90::/32 634 100% 67
2804:4f90:8000::/34 Valid Nonecovered by 2804:4f90::/32 634 100% 67
2804:4f90:c000::/34 Valid Nonecovered by 2804:4f90::/32 634 100% 67
45.238.100.0/22 Valid Other IRR onlyALTDB, RADB, TC 671 100% 67
2804:4f90::/32 Valid Other IRR onlyALTDB, RADB, TC 633 100% 67

AS-SET

AS268335'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 17 are in fix.csv.

  • ROA: none1
  • Route object: none13
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none38.211.113.0/24No ROA covers it. Add a ROA for AS268335, maxLength 24.669 of 673
Route object: RIR38.211.113.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: none45.238.100.0/23No route object for it. A route object for 45.238.100.0/22 with origin AS268335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268335 in the RIR database for the space.671 of 673
Route object: none45.238.102.0/23No route object for it. A route object for 45.238.100.0/22 with origin AS268335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268335 in the RIR database for the space.671 of 673
Route object: none45.238.100.0/24No route object for it. A route object for 45.238.100.0/22 with origin AS268335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268335 in the RIR database for the space.669 of 673
Route object: none45.238.101.0/24No route object for it. A route object for 45.238.100.0/22 with origin AS268335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268335 in the RIR database for the space.669 of 673
Route object: none45.238.102.0/24No route object for it. A route object for 45.238.100.0/22 with origin AS268335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268335 in the RIR database for the space.669 of 673
Route object: none45.238.103.0/24No route object for it. A route object for 45.238.100.0/22 with origin AS268335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268335 in the RIR database for the space.669 of 673
Route object: none2804:4f90::/34No route object for it. A route object for 2804:4f90::/32 with origin AS268335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268335 in the RIR database for the space.634 of 636
Route object: none2804:4f90:200::/40No route object for it. A route object for 2804:4f90::/32 with origin AS268335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268335 in the RIR database for the space.634 of 636
Route object: none2804:4f90:200::/41No route object for it. A route object for 2804:4f90::/32 with origin AS268335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268335 in the RIR database for the space.634 of 636
Route object: none2804:4f90:4000::/34No route object for it. A route object for 2804:4f90::/32 with origin AS268335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268335 in the RIR database for the space.634 of 636
Route object: none2804:4f90:4001::/48No route object for it. A route object for 2804:4f90::/32 with origin AS268335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268335 in the RIR database for the space.634 of 636
Route object: none2804:4f90:8000::/34No route object for it. A route object for 2804:4f90::/32 with origin AS268335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268335 in the RIR database for the space.634 of 636
Route object: none2804:4f90:c000::/34No route object for it. A route object for 2804:4f90::/32 with origin AS268335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268335 in the RIR database for the space.634 of 636
Route object: RIR45.238.100.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:4f90::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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