bgpreport

Network · data from 2026-11-12

AS267535 Ajust Consulting

Registry name: AS267535 - Ajust Consulting, BR · PeeringDB

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

Announced routes

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

2804:42e4::/34 Valid Nonecovered by 2804:42e4::/33 3 0%low visibility 3
2804:42e4:4000::/34 Valid Nonecovered by 2804:42e4::/33 3 0%low visibility 3
2804:42e4:8000::/34 Valid Nonecovered by 2804:42e4:8000::/33 3 0%low visibility 3
2804:42e4:c000::/34 Valid Nonecovered by 2804:42e4:8000::/33 3 0%low visibility 3
192.141.106.0/23 Valid Other IRR onlyRADB, TC 671 100% 66
192.141.105.0/24 Valid Other IRR onlyTC 669 99% 66
2804:42e4::/32 Valid Other IRR onlyRADB, TC 632 99% 67
2804:42e4::/33 Valid Other IRR onlyRADB 354 56% 64
2804:42e4:8000::/33 Valid Other IRR onlyRADB 354 56% 64
192.141.107.0/24 Valid Other IRR onlyRADB 185 27% 51
192.141.106.0/24 Valid Other IRR onlyRADB, TC 183 27% 51
192.141.104.0/24 Valid Other IRR onlyTC 3 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS267535: AS267535. 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 (AS267535 isn't in the set, or no route object for AS267535 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 objectsAS267535 in itNot covered
AS267535 A single AS number, not a set: AS267535 (this network), 18 route objects.

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

  • Route object: none4
  • Route object: RIR8
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: none2804:42e4::/34No route object for it. A route object for 2804:42e4::/33 with origin AS267535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267535 in the RIR database for the space.3 of 636
Route object: none2804:42e4:4000::/34No route object for it. A route object for 2804:42e4::/33 with origin AS267535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267535 in the RIR database for the space.3 of 636
Route object: none2804:42e4:8000::/34No route object for it. A route object for 2804:42e4:8000::/33 with origin AS267535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267535 in the RIR database for the space.3 of 636
Route object: none2804:42e4:c000::/34No route object for it. A route object for 2804:42e4:8000::/33 with origin AS267535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267535 in the RIR database for the space.3 of 636
Route object: RIR192.141.106.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR192.141.105.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:42e4::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:42e4::/33Route object only in RADB. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:42e4:8000::/33Route object only in RADB. Add it in the RIR database for the space.354 of 636
Route object: RIR192.141.107.0/24Route object only in RADB. Add it in the RIR database for the space.185 of 673
Route object: RIR192.141.106.0/24Route object only in RADB, TC. Add it in the RIR database for the space.183 of 673
Route object: RIR192.141.104.0/24Route object only in TC. Add it in the RIR database for the space.3 of 673

Route objects not announced

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

192.141.104.0/22RADB, TCValid
192.141.104.0/23TCValid
2804:85b8::/33RADBNo ROA
2804:85b8::/34RADBNo ROA
2804:85b8::/35RADBNo ROA
2804:85b8:2000::/35RADBNo ROA
2804:85b8:4000::/34RADBNo ROA
2804:85b8:8000::/33RADBNo ROA
2804:85b8:8000::/34RADBNo ROA
2804:85b8:c000::/34RADBNo 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.