bgpreport

Network · data from 2026-11-12

AS28572 Apoiocom Digital Ltda - EPP

Registry name: AS28572 - Apoiocom Digital Ltda - EPP, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28572, 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:6e3c:6400::/40 Valid Nonecovered by 2804:6e3c::/33 630 99% 67
200.192.146.0/24 Valid Other IRR onlyRADB 668 99% 66
200.192.144.0/24 Valid Other IRR onlyRADB 667 99% 66
200.192.146.0/23 Valid Other IRR onlyRADB 667 99% 66
200.192.147.0/24 Valid Other IRR onlyRADB 667 99% 67
200.192.148.0/22 Valid Other IRR onlyRADB 667 99% 66
200.192.151.0/24 Valid Other IRR onlyRADB 667 99% 67
200.192.156.0/24 Valid Other IRR onlyRADB 667 99% 67
200.192.157.0/24 Valid Other IRR onlyRADB 667 99% 67
200.192.159.0/24 Valid Other IRR onlyRADB 667 99% 67
200.192.145.0/24 Valid Other IRR onlyRADB 666 99% 66
200.192.158.0/24 Valid Other IRR onlyRADB 666 99% 67
200.192.149.0/24 Valid Other IRR onlyRADB 665 99% 66
200.192.150.0/24 Valid Other IRR onlyRADB 664 99% 66
200.192.148.0/24 Valid Other IRR onlyRADB 663 99% 67
2804:6e3c:4200::/39 Valid Other IRR onlyRADB 632 99% 67
2804:6e3c:5c00::/38 Valid Other IRR onlyRADB 630 99% 67
2804:6e3c::/32 Valid Other IRR onlyRADB 629 99% 67
2804:6e3c::/33 Valid Other IRR onlyRADB 629 99% 67
2804:6e3c:6000::/38 Valid Other IRR onlyRADB 629 99% 67
2804:6e3c:8000::/33 Valid Other IRR onlyRADB 629 99% 67
2804:6e3c:4000::/39 Valid Other IRR onlyRADB 626 98% 70
200.192.158.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS28572: AS-APOIOCOM-ALL. 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 (AS28572 isn't in the set, or no route object for AS28572 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 objectsAS28572 in itNot covered
AS-APOIOCOM-ALL RADB 2154 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 34 are in fix.csv.

  • Route object: none1
  • Route object: RIR22
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
Route object: none2804:6e3c:6400::/40No route object for it. A route object for 2804:6e3c::/33 with origin AS28572 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28572 in the RIR database for the space.630 of 636
Route object: RIR200.192.146.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.192.144.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR200.192.146.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR200.192.147.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR200.192.148.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR200.192.151.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR200.192.156.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR200.192.157.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR200.192.159.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR200.192.145.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR200.192.158.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR200.192.149.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR200.192.150.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR200.192.148.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673
Route object: RIR2804:6e3c:4200::/39Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:6e3c:5c00::/38Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:6e3c::/32Route object only in RADB. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:6e3c::/33Route object only in RADB. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:6e3c:6000::/38Route object only in RADB. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:6e3c:8000::/33Route object only in RADB. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:6e3c:4000::/39Route object only in RADB. Add it in the RIR database for the space.626 of 636
Route object: RIR200.192.158.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

200.192.144.0/20RADBNo ROA
200.192.144.0/21RADBNo ROA
200.192.144.0/22RADBValid
200.192.144.0/23RADBValid
200.192.148.0/23RADBValid
200.192.150.0/23RADBValid
200.192.156.0/22RADBValid
200.192.156.0/23RADBValid
2804:6e3c:4400::/38RADBValid
2804:6e3c:4800::/38RADBValid
2804:6e3c:4c00::/38RADBValid

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.