AS200680 CONECT-AS Marcin Barszcz trading as Conect
🇵🇱Org handle: ORG-MBTA12-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,536
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 109.207.68.0/22 | 🇵🇱 PL | RIPENCC | allocated |
| 109.207.68.0/23 | 🇵🇱 PL | RIPE | assigned |
| 2a0d:47c0::/29 | 🇵🇱 PL | RIPENCC | allocated |
All 1 announced prefix of AS200680 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS200680 hands its own prefixes to: transit providers, or peers at an exchange.
- AS35179KORBANK S. A1
Downstreams (1)
Networks whose own prefixes AS200680 passes on: usually its customers.
- AS198637ZPUE S.A1
Other adjacent networks (1)
Adjacent to AS200680 in the transit part of AS paths: peers, providers or customers.
- AS29535MIX2 OpenPeering Orange Polska Spolka Akcyjna1
ASPA
No ASPA
Abuse Contact
External Links
Learn more
- 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 AS200680 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
Open https://api.ipctl.io/v1/asn/200680Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/200680" | jq