Skip to main content

AS263396

ASN263396

BK Telecomunicações LTDA

Registry

Authoritative registration data

AS number
263396
Name
ASN263396
Organisation
BK Telecomunicações LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

3

Total announced

8

Announced prefixes

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

Prefixes announced by AS263396
177.125.252.0/22 IPv4 /22 not checked
177.125.252.0/23 IPv4 /23 not checked
177.125.254.0/23 IPv4 /23 not checked
177.125.252.0/24 IPv4 /24 not checked
177.125.255.0/24 IPv4 /24 not checked
2804:1594::/32 IPv6 /32 not checked
2804:1594:8000::/33 IPv6 /33 not checked
2804:1594::/33 IPv6 /33 not checked

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 AS263396
Address families
IX.br (PTT.br) Aracaju: ATM/MLPA 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 AS263396 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS263396 in AS paths

Observed upstreams
Families
AS263321 ASN263321 1,931 6,112
v4 v6
AS52901 ASN52901 1,380 5,539
v4 v6

No rows match “”.

Showing – of

Observed downstreams

8 networks seen after AS263396 in AS paths

Observed downstreams
Families
AS268026 800 2,885
v4 v6
AS271001 ASN271001 837 2,854
v4 v6
AS271311 ASN271311 694 2,495
v4 v6
AS267130 ASN267130 146 206
v4 v6
AS263287 ASN263287 124 177
v4 v6
AS266068 ASN266068 98 132
v4
AS266589 ASN266589 35 51
v4
AS267086 ASN267086 4 4
v4

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS28624 ASN28624 2 5
v4 v6

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.