AS206013 PINGDAY-ASN Pingday AB

🇸🇪

Org handle: ORG-PA1355-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

5total

4 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)3,072

Announced (BGP)3,072

IPv6 Addresses

Allocated (RIR)1.2×10²⁴

Announced (BGP)1.2×10²⁴

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2022-04-12

Announced Prefixes

(BGP)5

Prefix	RPKI	IRR	Last Seen
193.180.104.0/21	Valid	RIPE	2026-10-11
193.180.112.0/23	Valid	RIPE	2026-10-11
193.180.114.0/24	Valid	RIPE	2026-10-11
194.14.33.0/24	Valid	RIPE	2026-10-11
2001:67c:10e4::/48	Valid	RIPE	2026-10-11

(RIR)5

Prefix	Country	RIR	Status
193.180.104.0/21	🇸🇪 SE	RIPE	assigned
193.180.112.0/23	🇸🇪 SE	RIPE	assigned
193.180.114.0/24	🇸🇪 SE	RIPE	assigned
194.14.33.0/24	🇸🇪 SE	RIPE	assigned
2001:67c:10e4::/48	🇸🇪 SE	RIPENCC	assigned

(seen in AS paths)

Networks AS206013 hands its own prefixes to: transit providers, or peers at an exchange.

ASPA

No ASPA

Abuse Contact

External Links

What is an ASN?Autonomous systems, ASN ranges and how they are assigned
RPKI and route origin validationWhat the RPKI badges on the prefix list mean
ASPA explainedWhy AS206013 should publish an ASPA object
IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/206013" | jq