Skip to main content

AS268056

ASN268056

LEXCOM TELECOM

Registry

Authoritative registration data

AS number
268056
Name
ASN268056
Organisation
LEXCOM TELECOM
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

3

Total announced

10

Announced prefixes

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

Prefixes announced by AS268056
45.168.88.0/22 IPv4 /22 RPKI valid
45.168.88.0/23 IPv4 /23 RPKI valid
45.168.90.0/23 IPv4 /23 not checked
45.168.88.0/24 IPv4 /24 not checked
45.168.89.0/24 IPv4 /24 RPKI valid
45.168.90.0/24 IPv4 /24 RPKI valid
45.168.91.0/24 IPv4 /24 not checked
2804:5748::/32 IPv6 /32 RPKI valid
2804:5748:8000::/33 IPv6 /33 RPKI valid
2804:5748::/33 IPv6 /33 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 AS268056
Address families
IX.br (PTT.br) Fortaleza: ATM/MPLA 40,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Rio de Janeiro: ATM/MPLA 20,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Salvador: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: 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 AS268056 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS268056 in AS paths

Observed upstreams
Families
AS23106 ASN23106 557 736
v4 v6
AS6939 HURRICANE 153 730
v4 v6
AS52720 ASN52720 69 92
v4 v6
AS35280 F5 8 71
v4 v6
AS137409 GSLNETWORKS-AS-AP 9 44
v4 v6
AS6057 6057 4 22
v4 v6
AS39120 CONVERGENZE-AS 1 8
v4 v6
AS61626 ASN61626 1 8
v4 v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS268056 in AS paths

Observed downstreams
Families
AS272654 ASN272654 274 347
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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