bgpreport

Network · data from 2026-11-12

AS268024 A. H. SANTOS OLIVEIRA

Registry name: AS268024 - TURBONET CAXIAS, BR · 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
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS268024, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268024, 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.168.44.0/23 No ROA Other IRR onlyBBOI, RADB 671 100% 66
45.168.46.0/24 No ROA Other IRR onlyRADB 671 100% 66
45.168.44.0/24 No ROA Other IRR onlyRADB 669 99% 66
45.168.45.0/24 No ROA Other IRR onlyRADB 669 99% 66
45.168.47.0/24 No ROA Other IRR onlyRADB 666 99% 67
2804:56cc:c000::/40 No ROA Other IRR onlyRADB 635 100% 69
2804:56cc::/33 No ROA Other IRR onlyRADB 631 99% 67
2804:56cc::/34 No ROA Other IRR onlyRADB 631 99% 67
2804:56cc:4000::/34 No ROA Other IRR onlyRADB 631 99% 67
2804:56cc:8000::/34 No ROA Other IRR onlyRADB 631 99% 67

AS-SET

PeeringDB's irr_as_set for AS268024: AS268024:AS-CUST. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS268024 isn't in the set, or no route object for AS268024 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS268024 in itNot covered
AS268024:AS-CUST In no IRR database read today.

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
  • AS-SET: not found1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none45.168.44.0/23No ROA covers it. Add a ROA for AS268024, maxLength 23.671 of 673
Route object: RIR45.168.44.0/23Route object only in BBOI, RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.168.46.0/24No ROA covers it. Add a ROA for AS268024, maxLength 24.671 of 673
Route object: RIR45.168.46.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.168.44.0/24No ROA covers it. Add a ROA for AS268024, maxLength 24.669 of 673
Route object: RIR45.168.44.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none45.168.45.0/24No ROA covers it. Add a ROA for AS268024, maxLength 24.669 of 673
Route object: RIR45.168.45.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none45.168.47.0/24No ROA covers it. Add a ROA for AS268024, maxLength 24.666 of 673
Route object: RIR45.168.47.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none2804:56cc:c000::/40No ROA covers it. Add a ROA for AS268024, maxLength 40.635 of 636
Route object: RIR2804:56cc:c000::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:56cc::/33No ROA covers it. Add a ROA for AS268024, maxLength 33.631 of 636
Route object: RIR2804:56cc::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:56cc::/34No ROA covers it. Add a ROA for AS268024, maxLength 34.631 of 636
Route object: RIR2804:56cc::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:56cc:4000::/34No ROA covers it. Add a ROA for AS268024, maxLength 34.631 of 636
Route object: RIR2804:56cc:4000::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:56cc:8000::/34No ROA covers it. Add a ROA for AS268024, maxLength 34.631 of 636
Route object: RIR2804:56cc:8000::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
AS-SET: not foundAS268024:AS-CUSTPeeringDB names AS268024:AS-CUST; no IRR database read has it.

Route objects not announced

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

45.168.44.0/22BBOI, RADB, TCNo ROA
45.168.46.0/23BBOI, RADBNo ROA
2804:56cc::/32BBOI, RADB, 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.