Tubaron Telecom
AS262903 is Tubaron Telecom (tubaron.com.br). It announces 7,168 IPv4 addresses in 25 prefixes, and 5 IPv6 prefixes.
Brazil· LACNIC· allocated 2011-02-03· isp
Where its space is
The IPv4 it announces that IP Geolocation places, by country. A /24 counts for the AS announcing most of it.
- Brazil124 · 100.00%
Registry record
Its ASN Whois record, as the registry publishes it.
- name
- Tubaron Telecom
- org
- 07775840000175
- org name
- Tubaron Telecom
- country
- BR
- source
- lacnic
- status
- DIRECT ALLOCATION
- created
- 2011-02-03
- updated
- 2018-01-06
- descr
- Tubaron Telecom
- abuse
- JOFGO15
- abuse name
- José Felipe Gorniski
- abuse kind
- role
- admin
- JOFGO15
- admin name
- José Felipe Gorniski
- admin kind
- role
What the databases see
Addresses each address-keyed database holds in the IPv4 it announces, as a share of that space, with its largest providers. Counts overlap.
- VPN IP610.85%
- novada, dataimpulse, 711proxy7.87%
- None here
- None here
- None here
- None here
- Hosting IP2,04828.57%
- None here
- None here
- None here
- SSH IP330.46%
- SMTP IP140.20%
- 0.28%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 177.23.208.0/22 | — | valid | 17 | 2026-10-02 |
| 177.23.208.0/23 | — | valid | 17 | 2026-10-02 |
| 177.23.208.0/24 | — | valid | 17 | 2026-10-02 |
| 177.23.210.0/23 | — | valid | 17 | 2026-10-02 |
| 177.23.212.0/22 | — | valid | 17 | 2026-10-02 |
| 177.23.212.0/23 | — | valid | 17 | 2026-10-02 |
| 177.23.212.0/24 | — | valid | 17 | 2026-10-02 |
| 177.23.214.0/23 | — | valid | 17 | 2026-10-02 |
| 177.86.104.0/21 | — | valid | 17 | 2026-10-02 |
| 177.86.104.0/22 | — | valid | 17 | 2026-10-02 |
| 177.86.104.0/23 | — | valid | 17 | 2026-10-02 |
| 177.86.106.0/23 | — | valid | 17 | 2026-10-02 |
| 177.86.108.0/22 | — | valid | 17 | 2026-10-02 |
| 177.86.108.0/23 | — | valid | 17 | 2026-10-02 |
| 177.86.110.0/23 | — | valid | 17 | 2026-10-02 |
| 179.109.56.0/21 | — | valid | 17 | 2026-10-02 |
| 179.109.56.0/22 | — | valid | 17 | 2026-10-02 |
| 179.109.56.0/23 | — | valid | 17 | 2026-10-02 |
| 179.109.58.0/23 | — | valid | 17 | 2026-10-02 |
| 179.109.60.0/22 | — | valid | 17 | 2026-10-02 |
| 179.109.60.0/23 | — | valid | 17 | 2026-10-02 |
| 179.109.62.0/23 | — | valid | 17 | 2026-10-02 |
| 186.251.56.0/22 | — | valid | 17 | 2026-10-02 |
| 186.251.56.0/23 | — | valid | 17 | 2026-10-02 |
| 186.251.58.0/23 | — | valid | 17 | 2026-10-02 |
IPv6 prefixes
Every IPv6 prefix BGP Route saw it announce.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 2804:1644::/32 | — | valid | 20 | 2026-10-02 |
| 2804:1644:f600::/40 | — | valid | 20 | 2026-10-02 |
| 2804:1644:fa00::/40 | — | valid | 20 | 2026-10-02 |
| 2804:1644:fb00::/40 | — | valid | 20 | 2026-10-02 |
| 2804:1644:fe00::/40 | — | valid | 20 | 2026-10-02 |
Test the real build first.
An evaluation license puts a full current build in your hands — every row, every column, no sampling — so you can measure it against your own traffic before anyone talks about terms.