Routing security
AS49974 BODATA
Unclassified RIPE Cable/DSL/ISP
Announcements
What this network originates
Every prefix observed with AS49974 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a00:9540::/32 | RPKI valid | IRR | 30 |
| 37.35.96.0/22 | RPKI valid | IRR | 52 |
| 37.35.100.0/24 | RPKI valid | IRR | 52 |
| 37.35.101.0/24 | RPKI valid | IRR | 52 |
| 37.35.102.0/24 | RPKI valid | IRR | 52 |
| 37.35.103.0/24 | RPKI valid | IRR | 52 |
| 45.157.164.0/22 | RPKI valid | IRR | 52 |
| 185.18.0.0/22 | RPKI valid | IRR | 52 |
| 213.5.32.0/21 | RPKI valid | IRR | 52 |
| 2001:67c:238::/48 | RPKI valid | IRR | 30 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS49974 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 37.35.96.0/22 | /22 | RIPENCC |
| 37.35.100.0/24 | /24 | RIPENCC |
| 37.35.101.0/24 | /24 | RIPENCC |
| 37.35.102.0/24 | /24 | RIPENCC |
| 37.35.103.0/24 | /24 | RIPENCC |
| 45.157.164.0/22 | /22 | RIPENCC |
| 185.18.0.0/22 | /22 | RIPENCC |
| 213.5.32.0/21 | /21 | RIPENCC |
| 2001:67c:238::/48 | /48 | RIPENCC |
| 2a00:9540::/32 | /32 | 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 |
|---|---|---|---|
| AS3292 | TDC Holding A/S | Declared | Observed |
| AS43557 | unnamed | Declared | not observed |
| AS39642 | Sinal A/S | not 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 AS49974 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.35.96.0/22 | RIPE | Bo Data ApS IPv4 PA-1 | MNT-BODATA | 2012-02-14 | Announced |
| 37.35.100.0/24 | RIPE | Bo Data ApS IPv4 PA-1 | MNT-BODATA | 2012-02-14 | Announced |
| 37.35.101.0/24 | RIPE | Bo Data ApS IPv4 PA-1 | MNT-BODATA | 2012-02-14 | Announced |
| 37.35.102.0/24 | RIPE | Bo Data ApS IPv4 PA-1 | MNT-BODATA | 2012-02-14 | Announced |
| 37.35.103.0/24 | RIPE | Bo Data route obj. | MNT-BODATA | 2012-01-06 | Announced |
| 45.157.164.0/22 | RIPE | Partner-IT.dk IPv4 route Obj. 30.09.2019 TK | MNT-THOMASKRUSE | 2019-09-30 | Announced |
| 185.18.0.0/22 | RIPE | ** Bo Data PA ** | MNT-BODATA | 2014-04-07 | Announced |
| 213.5.32.0/21 | RIPE | ** BoData ApS - route obj ** | MNT-BODATA | 2015-01-19 | Announced |
| 2001:67c:238::/48 | RIPE | ** BoData ApS - IPv6 - route OBJ ** | MNT-BODATA | 2011-01-24 | Announced |
| 2a00:9540::/32 | RIPE | BO Data ApS IPv6 PA prefix-1 | MNT-BODATA | 2012-02-14 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS49974 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-BODATA | RIPE | Lists AS49974 as a direct member |
AS-TDCNETDK | RIPE | Lists AS49974 as a direct member |
RPKI from rpki-client, validated 2026-10-12 12:10 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-12. Cross-check on bgp.he.net.