What is wrong. Organisation names of Brazilian ASes show replacement characters, for example "Brasrede Telecomunica��es LTDA" for AS52751. LACNIC's own WHOIS answer for these ASes already holds the replacement characters, so nothing routewatch does with that answer can recover the name. LACNIC's answer for them carries NIC.br's copyright header: NIC.br runs the registry for Brazil, and its own server, whois.registro.br, sends the same records with the accents intact, in Latin-1.
What acceptable looks like. When LACNIC's answer for an AS comes from NIC.br, routewatch asks whois.registro.br for the same AS and stores the fields from that answer, decoded with the rule of #165. Check NIC.br's terms of use and rate limits for its WHOIS server, and keep the query within them.
Definition of done.
A test built from a recorded whois.registro.br answer stores "Brasrede Telecomunicações LTDA".
The fix in internal/whois; no test queries a live server.
**What is wrong.** Organisation names of Brazilian ASes show replacement characters, for example "Brasrede Telecomunica��es LTDA" for AS52751. LACNIC's own WHOIS answer for these ASes already holds the replacement characters, so nothing routewatch does with that answer can recover the name. LACNIC's answer for them carries NIC.br's copyright header: NIC.br runs the registry for Brazil, and its own server, `whois.registro.br`, sends the same records with the accents intact, in Latin-1.
**What acceptable looks like.** When LACNIC's answer for an AS comes from NIC.br, routewatch asks `whois.registro.br` for the same AS and stores the fields from that answer, decoded with the rule of https://git.eeqj.de/sneak/routewatch/issues/165. Check NIC.br's terms of use and rate limits for its WHOIS server, and keep the query within them.
**Definition of done.**
- A test built from a recorded `whois.registro.br` answer stores "Brasrede Telecomunicações LTDA".
- The fix in `internal/whois`; no test queries a live server.
- One reviewed PR into `next`, after https://git.eeqj.de/sneak/routewatch/issues/165 is merged.
Model: opus-5-5
clawbot
self-assigned this 2026-10-27 01:39:22 +01:00
Built in #179. When LACNIC's answer for an AS carries NIC.br's copyright notice, the client also asks whois.registro.br and stores the fields from NIC.br's answer, decoded as Latin-1. If that query fails, or NIC.br sends its reduced answer for a client over its limit, LACNIC's fields are kept. NIC.br publishes no query limit; its policy at https://registro.br/upp says only that it blocks bulk harvesting.
Model: opus-5-5
Built in https://git.eeqj.de/sneak/routewatch/pulls/179. When LACNIC's answer for an AS carries NIC.br's copyright notice, the client also asks `whois.registro.br` and stores the fields from NIC.br's answer, decoded as Latin-1. If that query fails, or NIC.br sends its reduced answer for a client over its limit, LACNIC's fields are kept. NIC.br publishes no query limit; its policy at https://registro.br/upp says only that it blocks bulk harvesting.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What is wrong. Organisation names of Brazilian ASes show replacement characters, for example "Brasrede Telecomunica��es LTDA" for AS52751. LACNIC's own WHOIS answer for these ASes already holds the replacement characters, so nothing routewatch does with that answer can recover the name. LACNIC's answer for them carries NIC.br's copyright header: NIC.br runs the registry for Brazil, and its own server,
whois.registro.br, sends the same records with the accents intact, in Latin-1.What acceptable looks like. When LACNIC's answer for an AS comes from NIC.br, routewatch asks
whois.registro.brfor the same AS and stores the fields from that answer, decoded with the rule of #165. Check NIC.br's terms of use and rate limits for its WHOIS server, and keep the query within them.Definition of done.
whois.registro.branswer stores "Brasrede Telecomunicações LTDA".internal/whois; no test queries a live server.next, after #165 is merged.Model: opus-5-5
Built in #179. When LACNIC's answer for an AS carries NIC.br's copyright notice, the client also asks
whois.registro.brand stores the fields from NIC.br's answer, decoded as Latin-1. If that query fails, or NIC.br sends its reduced answer for a client over its limit, LACNIC's fields are kept. NIC.br publishes no query limit; its policy at https://registro.br/upp says only that it blocks bulk harvesting.Model: opus-5-5