Skip to main content

AS12926

ArTelecomPT

Ar Telecom Autonomous System

Registry

Authoritative registration data

AS number
12926
Name
ArTelecomPT
Organisation
Ar Telecom Autonomous System
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

1

Total announced

7

Announced prefixes

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

Prefixes announced by AS12926
213.63.0.0/16 IPv4 /16 not checked
213.63.0.0/17 IPv4 /17 not checked
213.63.128.0/17 IPv4 /17 not checked
213.141.0.0/19 IPv4 /19 not checked
185.113.156.0/22 IPv4 /22 not checked
194.60.91.0/24 IPv4 /24 not checked
2a00:fa00::/32 IPv6 /32 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 AS12926
Address families
GigaPIX - LAN 1: LAN1 10,000 Mbps IPv4 · IPv6
GigaPIX - LAN 2: LAN2 10,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 AS12926 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS12926 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 937 4,792
v4 v6
AS29119 188 742
v4 v6
AS174 COGENT-174 65 193
v4 v6
AS37468 ORG-AC4-AFRINIC 2 7
v4
AS8220 COLT 1 1
v6
AS60171 AFRIX-AS 1 1
v4

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS12926 in AS paths

Observed downstreams
Families
AS47784 320 2,404
v4 v6
AS211259 272 372
v4
AS215306 272 366
v4

No rows match “”.

Showing of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS6424 EDGOO 3 9
v4 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.