Routing security
AS200482 NEXSERV
Unclassified RIPE NSP
Announcements
What this network originates
Every prefix observed with AS200482 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a12:3e80::/40 | RPKI valid | IRR | 31 |
| 2a12:3e80:401::/48 | RPKI valid | IRR | 32 |
| 2a12:3e80:403::/48 | RPKI valid | IRR | 31 |
| 2a12:3e80:404::/48 | RPKI valid | IRR | 31 |
| 37.114.35.0/24 | RPKI valid | IRR | 52 |
| 37.114.38.0/24 | RPKI valid | IRR | 52 |
| 37.114.60.0/24 | RPKI valid | IRR | 52 |
| 45.89.142.0/24 | RPKI valid | IRR | 52 |
| 45.142.112.0/24 | RPKI valid | IRR | 52 |
| 45.142.113.0/24 | RPKI valid | IRR | 52 |
| 109.71.254.0/24 | RPKI valid | IRR | 52 |
| 193.187.255.0/24 | RPKI valid | IRR | 52 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS200482 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 37.114.35.0/24 | /32 | RIPENCC |
| 37.114.38.0/24 | /24 | RIPENCC |
| 37.114.60.0/24 | /24 | RIPENCC |
| 37.114.61.0/24 | /24 | RIPENCC |
| 45.89.142.0/24 | /24 | RIPENCC |
| 45.142.112.0/24 | /24 | RIPENCC |
| 45.142.113.0/24 | /24 | RIPENCC |
| 109.71.254.0/24 | /24 | RIPENCC |
| 193.187.255.0/24 | /24 | RIPENCC |
| 2a07:6d40:2::/48 | /48 | RIPENCC |
| 2a12:3e80::/40 | /48 | RIPENCC |
| 2a12:3e80:401::/48 | /48 | RIPENCC |
| 2a12:3e80:403::/48 | /48 | RIPENCC |
| 2a12:3e80:404::/48 | /48 | RIPENCC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
This network has signed an ASPA record naming its transit providers. Each is compared against the upstreams observed in routing paths.
| AS | Network | ASPA | Routing paths |
|---|---|---|---|
| AS45014 | Nuco Technologies Ltd | Declared | not observed |
| AS48314 | Michael Sebastian Schinzel trading as IP-Projects GmbH & Co. KG | Declared | Observed |
| AS49192 | Openfactory GmbH | Declared | not observed |
| AS50629 | LWLcom GmbH | Declared | Observed |
An observed upstream that is not declared is not necessarily a leak: our upstream inference cannot tell a transit provider from a peer seen in the same position. A declared provider that is never observed is usually a backup path.
IRR
Registered route objects
Route objects naming AS200482 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 37.114.61.0/24 | RIPE | — | MNT-INTERCOLO | 2023-10-20 | Not announced |
| 37.114.35.0/24 | RIPE | — | MNT-INTERCOLO | 2024-11-07 | Announced |
| 37.114.38.0/24 | RIPE | AS200482 | MNT-INTERCOLO | 2025-03-07 | Announced |
| 37.114.60.0/24 | RIPE | — | MNT-INTERCOLO | 2023-01-30 | Announced |
| 45.89.142.0/24 | RIPE | — | LIR-DE-NEXSERV-1-MNT | 2025-08-24 | Announced |
| 45.142.112.0/24 | RIPE | — | MNT-LUMASERV | 2023-03-19 | Announced |
| 45.142.113.0/24 | RIPE | — | MNT-LUMASERV | 2023-03-19 | Announced |
| 109.71.254.0/24 | RIPE | — | MOS-IP-MNT | 2023-06-14 | Announced |
| 193.187.255.0/24 | RIPE | — | LIR-DE-NEXSERV-1-MNT | 2023-06-07 | Announced |
| 2a12:3e80::/40 | RIPE | — | LIR-DE-NEXSERV-1-MNT | 2023-08-01 | Announced |
| 2a12:3e80:401::/48 | RIPE | — | LIR-DE-NEXSERV-1-MNT | 2026-07-09 | Announced |
| 2a12:3e80:403::/48 | RIPE | — | LIR-DE-NEXSERV-1-MNT | 2025-07-09 | Announced |
| 2a12:3e80:404::/48 | RIPE | — | LIR-DE-NEXSERV-1-MNT | 2025-08-24 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS200482 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS200482:AS-NEXSERV | PeeringDB | Declared by the operator as its own set |
AS-TNF | RIPE | Lists AS200482 as a direct member |
AS-UNET-CUSTOMERS | RIPE | Lists AS200482 as a direct member |
AS200482:AS-NEXSERV | RIPE | Lists AS200482 as a direct member |
RPKI from rpki-client, validated 2026-10-14 18:17 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-14. Cross-check on bgp.he.net.