bgpreport

Network · data from 2026-11-12

AS51783 dedic-center-as The Center of Dedicated Servers LLC

Registry name: dedic-center-as The Center of Dedicated Servers LLC, RU · not in PeeringDB

6IPv4 routes 66.7% RPKI valid · 100.0% with a route object
3IPv6 routes 0.0% RPKI valid · 33.3% with a route object
2RPKI invalid 2 origin · 0 maxLength
3No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS51783, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS51783, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
2a11:77c5::/32 Invalid: origin Other origin only 3 0%low visibility 5
2a11:bdc6::/32 Invalid: origin Other origin only 3 0%low visibility 4
91.221.70.0/23 No ROA RIR databaseRIPE 673 100% 66
185.189.132.0/22 No ROA RIR databaseRIPE 673 100% 66
2a0b:e980::/29 No ROA RIR databaseRIPE 634 100% 67
85.143.168.0/22 Valid RIR databaseRIPE 673 100% 66
85.143.188.0/23 Valid RIR databaseRIPE 673 100% 66
5.8.66.0/24 Valid RIR databaseRIPE 672 100% 66
5.8.67.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS51783 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 8 are in fix.csv.

  • ROA: origin2
  • ROA: none3
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin2a11:77c5::/32ROAs covering it name AS48108, not AS51783. If AS51783 should announce it, add a ROA for AS51783.3 of 636
Route object: none2a11:77c5::/32Route objects for it name AS48108. Add a route object with origin AS51783 in the RIR database for the space.3 of 636
ROA: origin2a11:bdc6::/32ROAs covering it name AS48108, not AS51783. If AS51783 should announce it, add a ROA for AS51783.3 of 636
Route object: none2a11:bdc6::/32Route objects for it name AS48108. Add a route object with origin AS51783 in the RIR database for the space.3 of 636
ROA: none91.221.70.0/23No ROA covers it. Add a ROA for AS51783, maxLength 23.673 of 673
ROA: none185.189.132.0/22No ROA covers it. Add a ROA for AS51783, maxLength 22.673 of 673
ROA: none2a0b:e980::/29No ROA covers it. Add a ROA for AS51783, maxLength 29.634 of 636

Route objects not announced

Route objects with origin AS51783 whose prefix no peer sees AS51783 announce. Many are kept on purpose (backup routes, space announced only in some places).

2a04:ac00:3::/48RIPEValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.