Skip to main content

AS271758

ASN271758

Access World Services LTDA

Registry

Authoritative registration data

AS number
271758
Name
ASN271758
Organisation
Access World Services LTDA
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

5

Total announced

12

Announced prefixes

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

Prefixes announced by AS271758
131.100.28.0/22 IPv4 /22 not checked
131.100.28.0/23 IPv4 /23 not checked
131.100.30.0/23 IPv4 /23 not checked
131.100.28.0/24 IPv4 /24 not checked
131.100.29.0/24 IPv4 /24 not checked
131.100.30.0/24 IPv4 /24 not checked
131.100.31.0/24 IPv4 /24 not checked
2804:808c::/32 IPv6 /32 not checked
2804:808c:4000::/34 IPv6 /34 not checked
2804:808c:8000::/34 IPv6 /34 not checked
2804:808c::/34 IPv6 /34 not checked
2804:808c: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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS271758 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS271758 in AS paths

Observed upstreams
Families
AS268509 ASN268509 500 2,576
v4 v6
AS6939 HURRICANE 126 710
v4 v6
AS35280 F5 7 40
v4 v6
AS6057 6057 3 28
v4 v6
AS137409 GSLNETWORKS-AS-AP 4 16
v6
AS39120 CONVERGENZE-AS 1 4
v6
AS61626 ASN61626 1 4
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS271758 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.