bgpreport

Network · data from 2026-11-12

AS41033 D2 CLOUD COMMUNICATIONS

Registry name: D2-AS D2CLOUD NETWORK SERVICES (PTY) LTD, ZA · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
7IPv6 routes 71.4% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS41033, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS41033, 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.
2a0d:7100:6::/48 No ROA RIR databaseRIPE 634 100% 67
2a0d:7100:7::/48 No ROA RIR databaseRIPE 634 100% 67
185.46.237.0/24 Valid RIR databaseRIPE 672 100% 67
185.235.184.0/24 Valid RIR databaseRIPE 672 100% 67
185.235.185.0/24 Valid RIR databaseRIPE 672 100% 67
185.235.187.0/24 Valid RIR databaseRIPE 672 100% 67
2a0d:7100:3::/48 Valid RIR databaseRIPE 636 100% 67
2a0d:7100::/48 Valid RIR databaseRIPE 634 100% 67
2a0d:7100:2::/48 Valid RIR databaseRIPE 634 100% 67
2a0d:7100:4::/48 Valid RIR databaseRIPE 634 100% 67
2a0d:7100:5::/48 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS41033: AS-D2CLOUD. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS41033 isn't in the set, or no route object for AS41033 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS41033 in itNot covered
AS-D2CLOUD RIPElists itself further down6 member sets in no database: AS-AIREXPRESS, AS-HORS, AS-INFOBYTE-IFIX, AS-UNETCOM, AS-WINTELECOM … 1,17527814,636 Yes 0

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 12 are in fix.csv.

  • ROA: none2
  • AS-SET: missing member6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2a0d:7100:6::/48No ROA covers it. Add a ROA for AS41033, maxLength 48.634 of 636
ROA: none2a0d:7100:7::/48No ROA covers it. Add a ROA for AS41033, maxLength 48.634 of 636
AS-SET: missing memberAS-D2CLOUDAS-D2CLOUD (RIPE) lists AS-AIREXPRESS; no IRR database read has it.
AS-SET: missing memberAS-D2CLOUDAS-D2CLOUD (RIPE) lists AS-HORS; no IRR database read has it.
AS-SET: missing memberAS-D2CLOUDAS-D2CLOUD (RIPE) lists AS-INFOBYTE-IFIX; no IRR database read has it.
AS-SET: missing memberAS-D2CLOUDAS-D2CLOUD (RIPE) lists AS-UNETCOM; no IRR database read has it.
AS-SET: missing memberAS-D2CLOUDAS-D2CLOUD (RIPE) lists AS-WINTELECOM; no IRR database read has it.
AS-SET: missing memberAS-D2CLOUDAS-D2CLOUD (RIPE) lists AS199986:AS-SET; no IRR database read has it.

Route objects not announced

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

185.235.184.0/23RIPENo ROA
2a0d:7100:1::/48RIPEValid
2a0d:7100:8::/48RIPENo ROA
2a0d:7100:9::/48RIPENo ROA

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.