Autonomous system
AS208564 BEDROQ
Unclassified RIPE
Summary
Bedroq
business managed-it critical-infrastructure
The AS handle BEDROQ is held by Bedroq Limited.
What it's used for
- The address space carries mission-critical IT and operational technology for highly regulated UK organisations, as indicated by the netname
UK-BEDROQ-20190712and registrantBedroq Network Team. - The inventory consists of 1 IPv4 prefix (1024 addresses) with 2 observed neighbours, a ratio consistent with a business network providing managed services rather than mass-access residential or transit infrastructure.
- Traffic from this AS represents secure, resilient network connections and managed IT solutions for clients in sectors such as public safety and energy supply.
Notable
- Registrants align with the announcer, listing
Bedroq Network Team,Bedroq Limited, andAbuse-C Rolefor the announced prefix. - The address inventory is a single /22 block, indicating a consolidated corporate estate rather than fragmented or leased space.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-30, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 1.02K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| GB | United Kingdom | 1 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS208564- Registry name
- bedroq
- Registrant
- mnt-uk-bedroq-1
- Abuse contact
- abuse@bedroq.co.uk
- Registered
- 2019-07-12
- Last changed
- 2025-12-19
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Bedroq
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 2 valid, 0 with no ROA
- ROAs
- 2 authorising AS208564
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 4 naming AS208564
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 447 networks and 1,848 prefixes, as published 2026-10-31. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere