Skip to main content

AS266029

ASN266029

SBNET TELECOM

Registry

Authoritative registration data

AS number
266029
Name
ASN266029
Organisation
SBNET TELECOM
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

3

Total announced

10

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS266029
170.246.60.0/22 IPv4 /22 not checked
170.246.60.0/23 IPv4 /23 not checked
170.246.62.0/23 IPv4 /23 not checked
170.246.60.0/24 IPv4 /24 not checked
170.246.61.0/24 IPv4 /24 not checked
170.246.62.0/24 IPv4 /24 not checked
170.246.63.0/24 IPv4 /24 not checked
2804:3968::/32 IPv6 /32 RPKI valid
2804:3968:8000::/33 IPv6 /33 RPKI valid
2804:3968::/33 IPv6 /33 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS266029
Address families
IX.br (PTT.br) Curitiba: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Florianópolis: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS266029 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS266029 in AS paths

Observed upstreams
Families
AS53062 ASN53062 746 1,835
v4 v6
AS28146 ASN28146 77 330
v4 v6
AS6939 HURRICANE 66 232
v4
AS35280 F5 9 42
v4 v6
AS6057 6057 6 24
v4 v6
AS137409 GSLNETWORKS-AS-AP 6 24
v4
AS39120 CONVERGENZE-AS 1 4
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS266029 in AS paths

Observed downstreams
Families
AS272218 ASN272218 222 298
v6
AS267952 ASN267952 237 285
v4

No rows match “”.

Showing – of

Uncertain adjacencies

21 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.