bgpreport

Network · data from 2026-11-12

AS267101 ACB INFO TECNOLOGIA

Registry name: AS267101 - ACB Fibra, BR · PeeringDB

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

Announced routes

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

181.192.115.0/24 Valid Nonecovered by 181.192.112.0/22 670 100% 67
181.192.112.0/24 Valid Nonecovered by 181.192.112.0/22 669 99% 67
181.192.113.0/24 Valid Nonecovered by 181.192.112.0/22 669 99% 67
45.228.32.0/24 Valid Nonecovered by 45.228.32.0/22 668 99% 67
45.228.33.0/24 Valid Nonecovered by 45.228.32.0/22 668 99% 67
45.228.34.0/24 Valid Nonecovered by 45.228.32.0/22 668 99% 67
45.228.35.0/24 Valid Nonecovered by 45.228.32.0/22 668 99% 67
2804:4828:ff00::/40 Valid Nonecovered by 2804:4828::/32 635 100% 67
2804:4828:bf00::/40 Valid Nonecovered by 2804:4828::/32 634 100% 67
2804:4828::/33 Valid Nonecovered by 2804:4828::/32 632 99% 67
2804:4828:8000::/33 Valid Nonecovered by 2804:4828::/32 632 99% 67
45.228.34.0/23 Valid Nonecovered by 45.228.32.0/22 1 0%low visibility 1
45.228.32.0/22 Valid Other IRR onlyALTDB, NTTCOM, RADB, TC 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS267101: AS-267101. 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 (AS267101 isn't in the set, or no route object for AS267101 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 objectsAS267101 in itNot covered
AS-267101 ALTDB 214 Yes 0

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

  • Route object: none12
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none181.192.115.0/24No route object for it. A route object for 181.192.112.0/22 with origin AS267101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267101 in the RIR database for the space.670 of 673
Route object: none181.192.112.0/24No route object for it. A route object for 181.192.112.0/22 with origin AS267101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267101 in the RIR database for the space.669 of 673
Route object: none181.192.113.0/24No route object for it. A route object for 181.192.112.0/22 with origin AS267101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267101 in the RIR database for the space.669 of 673
Route object: none45.228.32.0/24No route object for it. A route object for 45.228.32.0/22 with origin AS267101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267101 in the RIR database for the space.668 of 673
Route object: none45.228.33.0/24No route object for it. A route object for 45.228.32.0/22 with origin AS267101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267101 in the RIR database for the space.668 of 673
Route object: none45.228.34.0/24No route object for it. A route object for 45.228.32.0/22 with origin AS267101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267101 in the RIR database for the space.668 of 673
Route object: none45.228.35.0/24No route object for it. A route object for 45.228.32.0/22 with origin AS267101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267101 in the RIR database for the space.668 of 673
Route object: none2804:4828:ff00::/40No route object for it. A route object for 2804:4828::/32 with origin AS267101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267101 in the RIR database for the space.635 of 636
Route object: none2804:4828:bf00::/40No route object for it. A route object for 2804:4828::/32 with origin AS267101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267101 in the RIR database for the space.634 of 636
Route object: none2804:4828::/33No route object for it. A route object for 2804:4828::/32 with origin AS267101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267101 in the RIR database for the space.632 of 636
Route object: none2804:4828:8000::/33No route object for it. A route object for 2804:4828::/32 with origin AS267101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267101 in the RIR database for the space.632 of 636
Route object: none45.228.34.0/23No route object for it. A route object for 45.228.32.0/22 with origin AS267101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267101 in the RIR database for the space.1 of 673
Route object: RIR45.228.32.0/22Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

181.192.112.0/22NTTCOM, RADBValid
2804:4828::/32ALTDB, NTTCOM, RADB, TCValid

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.