Skip to main content

AS263456

ASN263456

MKNETWORK TELECOM LTDA ME

Registry

Authoritative registration data

AS number
263456
Name
ASN263456
Organisation
MKNETWORK TELECOM LTDA ME
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

6

Total announced

10

Announced prefixes

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

Prefixes announced by AS263456
177.190.144.0/24 IPv4 /24 not checked
177.190.145.0/24 IPv4 /24 RPKI valid
177.190.146.0/24 IPv4 /24 not checked
177.190.147.0/24 IPv4 /24 RPKI valid
2804:1218:4000::/36 IPv6 /36 RPKI valid
2804:1218:8000::/36 IPv6 /36 RPKI valid
2804:1218:9000::/36 IPv6 /36 RPKI valid
2804:1218::/36 IPv6 /36 RPKI valid
2804:1218:a000::/36 IPv6 /36 RPKI not found
2804:1218:a000::/44 IPv6 /44 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 AS263456
Address families
IX.br (PTT.br) Belo Horizonte: ATM/MPLA 20,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Brasília: ATM/MPLA 10,000 Mbps IPv4 · IPv6
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 AS263456 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS263456 in AS paths

Observed upstreams
Families
AS23106 ASN23106 7,251 23,307
v4 v6
AS28198 ASN28198 1,052 2,685
v4 v6
AS263903 ASN263903 731 2,369
v4 v6
AS6939 HURRICANE 348 1,059
v4 v6
AS6057 6057 21 121
v4 v6
AS137409 GSLNETWORKS-AS-AP 23 97
v4
AS35280 F5 17 67
v4 v6
AS61626 ASN61626 2 2
v4
AS39120 CONVERGENZE-AS 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

14 networks seen after AS263456 in AS paths

Observed downstreams
Families
AS52967 ASN52967 2,635 14,051
v4 v6
AS263121 ASN263121 990 2,182
v4 v6
AS263031 ASN263031 551 2,101
v4
AS28198 ASN28198 1,044 1,876
v4
AS270587 ASN270587 910 1,847
v4 v6
AS266369 ASN266369 666 1,719
v4 v6
AS268241 ASN268241 388 1,213
v4
AS274387 ASN274387 273 696
v4
AS270644 ASN270644 315 432
v4 v6
AS266597 ASN266597 290 375
v4
AS274828 ASN274828 255 342
v6
AS270888 ASN270888 194 261
v4 v6
AS26456 JHASN-26456 9 34
v4
AS262529 ASN262529 9 10
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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