bgpreport

Network · data from 2026-11-12

AS61784 AltaNET Telecom

Registry name: AS61784 - AltaNet Telecom e Inf. LTDA-ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61784, 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:1948:3000::/36 Valid Nonecovered by 2804:1948::/33 635 100% 67
201.55.200.0/22 Valid Other IRR onlyRADB, TC 673 100% 66
138.186.184.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
201.55.202.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
2804:1948::/32 Valid Other IRR onlyRADB, TC 635 100% 67
201.55.200.0/23 Valid Other IRR onlyRADB, TC 203 30% 54
138.186.186.0/23 Valid Other IRR onlyRADB, TC 202 30% 54
138.186.184.0/23 Valid Other IRR onlyRADB, TC 200 30% 54
138.186.184.0/24 Valid Other IRR onlyRADB, TC 200 30% 54
138.186.185.0/24 Valid Other IRR onlyRADB, TC 200 30% 54
138.186.186.0/24 Valid Other IRR onlyRADB, TC 200 30% 54
138.186.187.0/24 Valid Other IRR onlyTC 200 30% 54
201.55.200.0/24 Valid Other IRR onlyTC 200 30% 54
201.55.201.0/24 Valid Other IRR onlyRADB, TC 200 30% 54
201.55.202.0/23 Valid Other IRR onlyRADB, TC 200 30% 54
201.55.203.0/24 Valid Other IRR onlyRADB, TC 200 30% 54

AS-SET

PeeringDB's irr_as_set for AS61784: TC::AS61784:AS-CUSTOMERS. 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 (AS61784 isn't in the set, or no route object for AS61784 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 objectsAS61784 in itNot covered
TC::AS61784:AS-CUSTOMERS TC 118 No 16

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

  • Route object: none1
  • Route object: RIR15
  • AS-SET: own ASN1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none2804:1948:3000::/36No route object for it. A route object for 2804:1948::/33 with origin AS61784 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61784 in the RIR database for the space.635 of 636
Route object: RIR201.55.200.0/22Route object only in RADB, TC. Add it in the RIR database for the space.673 of 673
Route object: RIR138.186.184.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR201.55.202.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:1948::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR201.55.200.0/23Route object only in RADB, TC. Add it in the RIR database for the space.203 of 673
Route object: RIR138.186.186.0/23Route object only in RADB, TC. Add it in the RIR database for the space.202 of 673
Route object: RIR138.186.184.0/23Route object only in RADB, TC. Add it in the RIR database for the space.200 of 673
Route object: RIR138.186.184.0/24Route object only in RADB, TC. Add it in the RIR database for the space.200 of 673
Route object: RIR138.186.185.0/24Route object only in RADB, TC. Add it in the RIR database for the space.200 of 673
Route object: RIR138.186.186.0/24Route object only in RADB, TC. Add it in the RIR database for the space.200 of 673
Route object: RIR138.186.187.0/24Route object only in TC. Add it in the RIR database for the space.200 of 673
Route object: RIR201.55.200.0/24Route object only in TC. Add it in the RIR database for the space.200 of 673
Route object: RIR201.55.201.0/24Route object only in RADB, TC. Add it in the RIR database for the space.200 of 673
Route object: RIR201.55.202.0/23Route object only in RADB, TC. Add it in the RIR database for the space.200 of 673
Route object: RIR201.55.203.0/24Route object only in RADB, TC. Add it in the RIR database for the space.200 of 673
AS-SET: own ASNTC::AS61784:AS-CUSTOMERSAS61784 isn't in AS61784:AS-CUSTOMERS (TC) once expanded. Add AS61784 to it.

Route objects not announced

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

2804:1948::/33TCValid
2804:1948:8000::/33TCValid
2804:1948:f000::/36RADBValid

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.