Skip to main content

AS267121

ASN267121

ATPlus Telecom

Registry

Authoritative registration data

AS number
267121
Name
ASN267121
Organisation
ATPlus Telecom
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

23

IPv6 prefixes

5

Total announced

28

Announced prefixes

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

Prefixes announced by AS267121
187.84.148.0/22 IPv4 /22 not checked
45.229.104.0/22 IPv4 /22 not checked
187.84.148.0/23 IPv4 /23 not checked
187.84.150.0/23 IPv4 /23 not checked
45.229.104.0/23 IPv4 /23 not checked
45.229.106.0/23 IPv4 /23 not checked
104.234.41.0/24 IPv4 /24 not checked
104.234.84.0/24 IPv4 /24 not checked
104.234.90.0/24 IPv4 /24 not checked
151.247.210.0/24 IPv4 /24 not checked
151.247.211.0/24 IPv4 /24 not checked
177.10.89.0/24 IPv4 /24 not checked
187.84.148.0/24 IPv4 /24 not checked
187.84.149.0/24 IPv4 /24 not checked
187.84.150.0/24 IPv4 /24 not checked
187.84.151.0/24 IPv4 /24 not checked
45.147.226.0/24 IPv4 /24 not checked
45.229.104.0/24 IPv4 /24 not checked
45.229.105.0/24 IPv4 /24 not checked
45.229.106.0/24 IPv4 /24 not checked
45.229.107.0/24 IPv4 /24 not checked
50.114.180.0/24 IPv4 /24 not checked
50.114.61.0/24 IPv4 /24 not checked
2804:4870::/32 IPv6 /32 not checked
2804:4870:7000::/38 IPv6 /38 not checked
2804:4870:2000::/40 IPv6 /40 not checked
2804:4870:2f00::/40 IPv6 /40 not checked
2804:4870:3000::/40 IPv6 /40 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Observed adjacencies

Networks seen next to AS267121 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS267121 in AS paths

Observed upstreams
Families
AS3356 1,868 8,645
v4
AS53062 2,208 4,952
v4 v6
AS263998 298 400
v4
AS33182 267 339
v4
AS6939 164 326
v4 v6
AS14840 234 296
v4
AS6057 19 85
v4 v6

No rows match “”.

Showing of

Observed downstreams

8 networks seen after AS267121 in AS paths

Observed downstreams
Families
AS264194 534 1,688
v4
AS263014 535 1,351
v4
AS265005 459 774
v4
AS274504 499 703
v4 v6
AS264263 259 676
v4
AS61821 299 465
v4 v6
AS274569 259 364
v6
AS263018 260 338
v4

No rows match “”.

Showing of

Uncertain adjacencies

28 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 10 90
v4 v6
AS51185 10 82
v4 v6
AS271253 9 76
v4
AS28634 9 72
v4
AS60503 10 45
v4 v6
AS263237 10 45
v4 v6
AS263152 10 44
v4 v6
AS61573 10 43
v4 v6
AS36236 9 43
v4 v6
AS22548 10 42
v4 v6
AS199524 10 42
v4 v6
AS264479 10 42
v4 v6
AS53046 9 42
v4 v6
AS35280 9 38
v4 v6
AS52873 10 37
v4 v6
AS37721 9 37
v4 v6
AS198150 9 36
v4
AS262427 9 35
v4
AS29049 8 32
v4
AS28624 3 6
v6
AS265005 2 5
v4
AS264194 1 5
v4
AS263014 1 3
v4
AS264263 1 2
v4
AS274504 1 2
v4 v6
AS61821 1 1
v4
AS263018 1 1
v4
AS274569 1 1
v6

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.