Skip to main content

AS263328

ASN263328

Panda Network

Registry

Authoritative registration data

AS number
263328
Name
ASN263328
Organisation
Panda Network
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

3

Total announced

13

Announced prefixes

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

Prefixes announced by AS263328
170.0.56.0/22 IPv4 /22 not checked
191.7.184.0/22 IPv4 /22 not checked
45.164.104.0/22 IPv4 /22 not checked
170.0.56.0/23 IPv4 /23 not checked
170.0.58.0/23 IPv4 /23 not checked
191.7.184.0/23 IPv4 /23 not checked
191.7.186.0/23 IPv4 /23 not checked
45.164.104.0/23 IPv4 /23 not checked
45.164.106.0/23 IPv4 /23 not checked
191.7.184.0/24 IPv4 /24 not checked
2804:1468::/32 IPv6 /32 RPKI valid
2804:1468:8000::/36 IPv6 /36 RPKI valid
2804:1468::/36 IPv6 /36 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 AS263328
Address families
IX.br (PTT.br) São Paulo: ATM/MPLA 200,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 AS263328 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS263328 in AS paths

Observed upstreams
Families
AS37468 ORG-AC4-AFRINIC 237 2,204
v4 v6
AS3356 LEVEL3 105 883
v4 v6
AS52863 ASN52863 191 565
v4 v6
AS6939 HURRICANE 105 309
v6
AS10429 ASN10429 3 32
v4
AS6057 6057 2 24
v4 v6
AS137409 GSLNETWORKS-AS-AP 2 12
v4
AS61626 ASN61626 1 12
v4 v6
AS39120 CONVERGENZE-AS 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS263328 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

18 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.