Data as of Nov 3, 2026
31.207.76.0/23
1 residential-proxy exit · 30 daysBeget LLC
Residential-proxy exits
Proxy exits
1
0.20% of its addresses · 30 days
Oct 4, 2026 – Nov 2, 2026
Exits seen per day
1 observation
Network & registry
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Apr 2025
- Current origin since
- Apr 2025 · 1.5 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 31.207.76.0/23 | AS198610 | /24 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS198610 | RIPE | BEGET-MNT | May 6, 2025 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 31.207.76.0/24 | AS198610 | RIPE | BEGET-MNT | May 6, 2025 | |
| 31.207.77.0/24 | AS198610 | RIPE | BEGET-MNT | May 6, 2025 |
Whois
Registration for this announcement
- Range
- 31.207.74.0 - 31.207.77.255
- Netname
- RU-BEGET-20110502
- Registrant
- Beget LLC
- Registrant country
- RU
- Organization
- Beget LLC (ORG-BL131-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Apr 11, 2025
- Updated
- May 6, 2025
- Maintainer
- BEGET-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- May 2, 2011
- Status
- assigned
Report abuse
Abuse contact
- [email protected]
- Name
- Abuse-C Role
- Handle
- AR16577-RIPE