Skip to main content

AS265192

ASN265192

Mnet LTDA

Registry

Authoritative registration data

AS number
265192
Name
ASN265192
Organisation
Mnet LTDA
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

6

Total announced

11

Announced prefixes

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

Prefixes announced by AS265192
167.249.144.0/22 IPv4 /22 not checked
167.249.144.0/24 IPv4 /24 not checked
167.249.145.0/24 IPv4 /24 not checked
167.249.146.0/24 IPv4 /24 not checked
167.249.147.0/24 IPv4 /24 not checked
2804:2c10::/32 IPv6 /32 not checked
2804:2c10:8000::/33 IPv6 /33 not checked
2804:2c10::/33 IPv6 /33 not checked
2804:2c10:4000::/34 IPv6 /34 not checked
2804:2c10:8000::/34 IPv6 /34 not checked
2804:2c10::/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 AS265192
Address families
IX.br (PTT.br) Fortaleza: ATM/MPLA 40,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Luís: ATM/MPLA 20,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 40,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Teresina: ATM/MPLA 20,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 AS265192 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS265192 in AS paths

Observed upstreams
Families
AS269194 2,304 8,329
v4 v6
AS265269 ASN265269 1,346 4,502
v4 v6
AS6939 HURRICANE 893 3,793
v4 v6
AS273669 397 1,516
v4 v6
AS6057 6057 34 159
v4 v6
AS14840 ASN14840 2 15
v4

No rows match “”.

Showing of

Observed downstreams

11 networks seen after AS265192 in AS paths

Observed downstreams
Families
AS264576 562 5,361
v4 v6
AS269508 555 5,006
v4 v6
AS270441 1,125 2,141
v4 v6
AS263974 480 1,140
v4 v6
AS264180 540 714
v4 v6
AS266643 541 713
v4 v6
AS271566 367 688
v4 v6
AS271406 290 358
v4
AS267501 44 63
v6
AS269430 44 61
v4 v6
AS265144 1 1
v4

No rows match “”.

Showing of

Uncertain adjacencies

26 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 12 82
v4 v6
AS264479 13 63
v4 v6
AS61573 13 59
v4 v6
AS51185 MAINSTREAMING-AS 12 54
v4 v6
AS263152 12 46
v4 v6
AS22548 13 41
v4 v6
AS35280 F5 13 41
v4 v6
AS60503 12 40
v4 v6
AS36236 NETACTUATE 11 35
v4 v6
AS262427 11 32
v4
AS263237 8 31
v6
AS52873 7 31
v6
AS271253 9 28
v4
AS28624 8 27
v6
AS28634 8 26
v4
AS199524 GCORE 8 13
v4
AS264576 1 11
v4 v6
AS269508 1 10
v4 v6
AS263974 2 4
v4 v6
AS270441 2 2
v6
AS264180 1 2
v4 v6
AS266643 1 2
v4 v6
AS29049 1 1
v4
AS198150 1 1
v4
AS271406 1 1
v4
AS271566 1 1
v4

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.