bgpreport

Network · data from 2026-11-12

AS264526 ASN264526

Registry name: AS264526 - ALPHANETT SERVICOS DE TELECOMUNICACOES, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264526, 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:2100:2000::/40 Valid Nonecovered by 2804:2100::/32 634 100% 67
2804:2100:2100::/40 Valid Nonecovered by 2804:2100::/32 634 100% 67
132.255.204.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
132.255.207.0/24 Valid Other IRR onlyRADB 669 99% 67
2804:2100::/32 Valid Other IRR onlyRADB, TC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS264526: TC::AS264526:AS-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 (AS264526 isn't in the set, or no route object for AS264526 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 objectsAS264526 in itNot covered
TC::AS264526:AS-ALL TC 123 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 5 are in fix.csv.

  • Route object: none2
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
Route object: none2804:2100:2000::/40No route object for it. A route object for 2804:2100::/32 with origin AS264526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264526 in the RIR database for the space.634 of 636
Route object: none2804:2100:2100::/40No route object for it. A route object for 2804:2100::/32 with origin AS264526 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264526 in the RIR database for the space.634 of 636
Route object: RIR132.255.204.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR132.255.207.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:2100::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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