bgpreport

Network · data from 2026-11-12

AS268018 Giga+ Fibra - Sergipe

Registry name: AS268018 - DB3 SERVICOS DE TELECOMUNICACOES S.A, BR · PeeringDB

28IPv4 routes 96.4% RPKI valid · 17.9% with a route object
2IPv6 routes 100.0% RPKI valid · 50.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
0No ROA 24 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS268018, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268018, 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.172.126.0/24 Invalid: origin Other origin only 2 0%low visibility 4
45.165.230.0/24 Valid Nonecovered by 45.165.230.0/23 672 100% 67
45.165.231.0/24 Valid Nonecovered by 45.165.230.0/23 672 100% 67
138.122.85.0/24 Valid Nonecovered by 138.122.84.0/22 672 100% 67
138.122.86.0/24 Valid Nonecovered by 138.122.84.0/22 672 100% 67
177.39.56.0/22 Valid Nonecovered by 177.39.56.0/21 672 100% 67
177.39.58.0/23 Valid Nonecovered by 177.39.56.0/21 672 100% 67
177.53.223.0/24 Valid Nonecovered by 177.53.216.0/21 672 100% 67
138.122.84.0/23 Valid Nonecovered by 138.122.84.0/22 670 100% 67
138.122.86.0/23 Valid Nonecovered by 138.122.84.0/22 670 100% 67
177.53.216.0/22 Valid Nonecovered by 177.53.216.0/21 670 100% 67
177.53.216.0/23 Valid Nonecovered by 177.53.216.0/21 670 100% 67
177.53.218.0/23 Valid Nonecovered by 177.53.216.0/21 670 100% 67
177.53.220.0/22 Valid Nonecovered by 177.53.216.0/21 670 100% 67
177.53.220.0/23 Valid Nonecovered by 177.53.216.0/21 670 100% 67
177.53.222.0/23 Valid Nonecovered by 177.53.216.0/21 670 100% 67
179.96.216.0/22 Valid Nonecovered by 179.96.216.0/21 670 100% 67
179.96.216.0/23 Valid Nonecovered by 179.96.216.0/21 670 100% 67
179.96.218.0/23 Valid Nonecovered by 179.96.216.0/21 670 100% 67
179.96.220.0/22 Valid Nonecovered by 179.96.216.0/21 670 100% 67
179.96.220.0/23 Valid Nonecovered by 179.96.216.0/21 670 100% 67
179.96.222.0/23 Valid Nonecovered by 179.96.216.0/21 670 100% 67
179.96.218.0/24 Valid Nonecovered by 179.96.216.0/21 667 99% 67
2804:56b0::/34 Valid Nonecovered by 2804:56b0::/32 632 99% 67
138.122.84.0/22 Valid Other IRR onlyRADB 672 100% 67
177.39.56.0/21 Valid Other IRR onlyRADB 672 100% 67
177.53.216.0/21 Valid Other IRR onlyRADB 672 100% 67
179.96.216.0/21 Valid Other IRR onlyRADB 672 100% 67
2804:56b0::/32 Valid Other IRR onlyRADB 632 99% 67
45.165.230.0/23 Valid Other IRR onlyRADB 509 76% 67

AS-SET

AS268018'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 31 are in fix.csv.

  • ROA: origin1
  • Route object: none24
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: origin45.172.126.0/24ROAs covering it name AS28598, not AS268018. If AS268018 should announce it, add a ROA for AS268018.2 of 673
Route object: none45.172.126.0/24Route objects for it name AS28598. Add a route object with origin AS268018 in the RIR database for the space.2 of 673
Route object: none45.165.230.0/24No route object for it. A route object for 45.165.230.0/23 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.672 of 673
Route object: none45.165.231.0/24No route object for it. A route object for 45.165.230.0/23 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.672 of 673
Route object: none138.122.85.0/24No route object for it. A route object for 138.122.84.0/22 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.672 of 673
Route object: none138.122.86.0/24No route object for it. A route object for 138.122.84.0/22 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.672 of 673
Route object: none177.39.56.0/22No route object for it. A route object for 177.39.56.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.672 of 673
Route object: none177.39.58.0/23No route object for it. A route object for 177.39.56.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.672 of 673
Route object: none177.53.223.0/24No route object for it. A route object for 177.53.216.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.672 of 673
Route object: none138.122.84.0/23No route object for it. A route object for 138.122.84.0/22 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.670 of 673
Route object: none138.122.86.0/23No route object for it. A route object for 138.122.84.0/22 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.670 of 673
Route object: none177.53.216.0/22No route object for it. A route object for 177.53.216.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.670 of 673
Route object: none177.53.216.0/23No route object for it. A route object for 177.53.216.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.670 of 673
Route object: none177.53.218.0/23No route object for it. A route object for 177.53.216.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.670 of 673
Route object: none177.53.220.0/22No route object for it. A route object for 177.53.216.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.670 of 673
Route object: none177.53.220.0/23No route object for it. A route object for 177.53.216.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.670 of 673
Route object: none177.53.222.0/23No route object for it. A route object for 177.53.216.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.670 of 673
Route object: none179.96.216.0/22No route object for it. A route object for 179.96.216.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.670 of 673
Route object: none179.96.216.0/23No route object for it. A route object for 179.96.216.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.670 of 673
Route object: none179.96.218.0/23No route object for it. A route object for 179.96.216.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.670 of 673
Route object: none179.96.220.0/22No route object for it. A route object for 179.96.216.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.670 of 673
Route object: none179.96.220.0/23No route object for it. A route object for 179.96.216.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.670 of 673
Route object: none179.96.222.0/23No route object for it. A route object for 179.96.216.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.670 of 673
Route object: none179.96.218.0/24No route object for it. A route object for 179.96.216.0/21 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.667 of 673
Route object: none2804:56b0::/34No route object for it. A route object for 2804:56b0::/32 with origin AS268018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268018 in the RIR database for the space.632 of 636
Route object: RIR138.122.84.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.39.56.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.53.216.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR179.96.216.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:56b0::/32Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR45.165.230.0/23Route object only in RADB. Add it in the RIR database for the space.509 of 673

Route objects not announced

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