2a04:18c0::/29 - FTS Fujitsu Technology Solutions BV (AS60941)
CIDR
2a04:18c0::/29
IP Version
IPv6
Addresses
633825.3Y
Mask
/29
Country
๐ณ๐ฑ The Netherlands
City
Maarssen
RIR
RIPE NCC
Status
allocated
Allocated
2013-03-08
Announced BGP Routes
0 of 0 routesRPKI:
IRR:
Swipe sideways to see all columns โ
| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| This prefix is not announced as a whole. Parts of it are announced as more-specific prefixes, see below. | ||||
More-Specific Announcements
11 more-specific announcements| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 2a04:18c0::/48 | AS60941 FTS Fujitsu Technology Solutions BV | No ROA | - | 2026-10-12 |
| 2a04:18c0:1::/48 | AS60941 FTS Fujitsu Technology Solutions BV | No ROA | - | 2026-10-12 |
| 2a04:18c0:2::/48 | AS60941 FTS Fujitsu Technology Solutions BV | No ROA | - | 2026-10-12 |
| 2a04:18c0:3::/48 | AS60941 FTS Fujitsu Technology Solutions BV | No ROA | - | 2026-10-12 |
| 2a04:18c0:4::/48 | AS60941 FTS Fujitsu Technology Solutions BV | No ROA | - | 2026-10-12 |
| 2a04:18c0:5::/48 | AS60941 FTS Fujitsu Technology Solutions BV | No ROA | - | 2026-10-12 |
| 2a04:18c0:6::/48 | AS60941 FTS Fujitsu Technology Solutions BV | No ROA | - | 2026-10-12 |
| 2a04:18c0:7::/48 | AS60941 FTS Fujitsu Technology Solutions BV | No ROA | - | 2026-10-12 |
| 2a04:18c0:8::/48 | AS60941 FTS Fujitsu Technology Solutions BV | No ROA | - | 2026-10-12 |
| 2a04:18c0:9::/48 | AS60941 FTS Fujitsu Technology Solutions BV | No ROA | - | 2026-10-12 |
| 2a04:18c0:a::/48 | AS60941 FTS Fujitsu Technology Solutions BV | No ROA | - | 2026-10-12 |
IRR Route Objects
| Origin | Registry | Maintainer | Modified |
|---|---|---|---|
| AS60941 | RIPE | FTS-MNT | 2015-02-06 |
More Specific Prefixes
| Prefix | AS | Country | Status |
|---|---|---|---|
| 2a04:18c0::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:1::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:2::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:3::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:4::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:5::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:6::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:7::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:8::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:9::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:a::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:b::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:c::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:d::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:e::/64 | ๐ณ๐ฑNL | assigned | |
| 2a04:18c0:0:f::/64 | ๐ณ๐ฑNL | assigned |
Related Prefixes
Geolocation
Abuse Contact
Learn more
- RPKI and ROAs explainedWhat RPKI valid, invalid and no ROA mean
- RPKI validatorCheck ROA coverage for any prefix or ASN
- What is BGP?How prefixes are announced and routed
- More-specific prefixesGlossary: covering and more-specific routes
- IPv4 transfers in the RIPE NCC regionWho bought and sold address space recently
API
Open https://api.ipctl.io/v1/prefix/2a04:18c0::/29Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/2a04:18c0::/29" | jq
External Links