Skip to main content

AS197064

EMITEL

ul. Franciszka Klimczaka 1

Registry

Authoritative registration data

AS number
197064
Name
EMITEL
Organisation
ul. Franciszka Klimczaka 1
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS197064
151.248.56.0/21 IPv4 /21 not checked
178.23.104.0/21 IPv4 /21 not checked
185.24.196.0/22 IPv4 /22 not checked
2a02:2408::/32 IPv6 /32 RPKI valid

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

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS197064 in AS paths

No rows match “”.

Showing – of

Observed downstreams

6 networks seen after AS197064 in AS paths

Observed downstreams
Families
AS197494 RADIO-WROCLAW-AS 269 483
v4
AS197513 RADIO-OLSZTYN 256 329
v4
AS201427 PL-M2M-AS 94 138
v4
AS62457 TVPULS 53 72
v4
AS60335 BS-LIMANOWA-AS 38 44
v4
AS43153 SFERANET-AS 24 27
v4

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 3 28
v4 v6
AS49544 i3Dnet 3 14
v4 v6
AS28917 Fiord-AS 6 11
v4 v6
AS36236 NETACTUATE 1 4
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.