Skip to main content

AS264999

ASN264999

UMPLAY TELECOM

Registry

Authoritative registration data

AS number
264999
Name
ASN264999
Organisation
UMPLAY TELECOM
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

7

Total announced

14

Announced prefixes

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

Prefixes announced by AS264999
170.84.76.0/22 IPv4 /22 not checked
170.84.76.0/23 IPv4 /23 not checked
170.84.78.0/23 IPv4 /23 not checked
170.84.76.0/24 IPv4 /24 not checked
170.84.77.0/24 IPv4 /24 not checked
170.84.78.0/24 IPv4 /24 not checked
170.84.79.0/24 IPv4 /24 not checked
2804:3130::/32 IPv6 /32 RPKI valid
2804:3130:8000::/33 IPv6 /33 not checked
2804:3130::/33 IPv6 /33 not checked
2804:3130:4000::/34 IPv6 /34 RPKI valid
2804:3130:8000::/34 IPv6 /34 RPKI valid
2804:3130::/34 IPv6 /34 RPKI valid
2804:3130:c000::/34 IPv6 /34 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 AS264999
Address families
IX.br (PTT.br) Fortaleza: 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 AS264999 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS264999 in AS paths

Observed upstreams
Families
AS265038 ASN265038 243 668
v4 v6
AS6939 HURRICANE 60 332
v4 v6
AS263907 ASN263907 211 294
v4 v6
AS35280 F5 3 36
v4 v6
AS6057 6057 3 20
v4 v6
AS61626 ASN61626 1 8
v4 v6
AS7195 7195 1 4
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS264999 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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