bgpreport

Network · data from 2026-11-12

AS271837 DESPLIEGUE COMPUTACIONAL E INTERNET DCNET

Registry name: AS271837 - DESPLIEGUE COMPUTACIONAL E INTERNET DCNET S.A., EC · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271837, 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.

2803:5810:2::/48 Valid Nonecovered by 2803:5810::/32 635 100% 67
2803:5810:7::/48 Valid Nonecovered by 2803:5810::/32 635 100% 67
2803:5810:8::/48 Valid Nonecovered by 2803:5810::/32 635 100% 67
2803:5810:e::/48 Valid Nonecovered by 2803:5810::/32 635 100% 67
2803:5810::/48 Valid Nonecovered by 2803:5810::/32 634 100% 67
2803:5810:4::/48 Valid Nonecovered by 2803:5810::/32 634 100% 67
2803:5810:5::/48 Valid Nonecovered by 2803:5810::/32 634 100% 67
2803:5810:6::/48 Valid Nonecovered by 2803:5810::/32 634 100% 67
2803:5810:9::/48 Valid Nonecovered by 2803:5810::/32 634 100% 67
2803:5810:a::/48 Valid Nonecovered by 2803:5810::/32 634 100% 67
2803:5810:b::/48 Valid Nonecovered by 2803:5810::/32 634 100% 67
2803:5810:c::/48 Valid Nonecovered by 2803:5810::/32 634 100% 67
2803:5810:d::/48 Valid Nonecovered by 2803:5810::/32 634 100% 67
2803:5810:f::/48 Valid Nonecovered by 2803:5810::/32 634 100% 67
179.63.20.0/24 Valid Other IRR onlyRADB 672 100% 67
179.63.21.0/24 Valid Other IRR onlyRADB 672 100% 67
179.63.22.0/24 Valid Other IRR onlyRADB 672 100% 67
179.63.23.0/24 Valid Other IRR onlyRADB 672 100% 67
179.63.20.0/22 Valid RIR databaseLACNIC, RADB 672 100% 67
177.234.228.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
2803:5810::/32 Valid RIR databaseLACNIC, RADB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS271837: AS-DCNETSA. 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 (AS271837 isn't in the set, or no route object for AS271837 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 objectsAS271837 in itNot covered
AS-DCNETSA In no IRR database read today.

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

  • Route object: none14
  • Route object: RIR4
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: none2803:5810:2::/48No route object for it. A route object for 2803:5810::/32 with origin AS271837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271837 in the RIR database for the space.635 of 636
Route object: none2803:5810:7::/48No route object for it. A route object for 2803:5810::/32 with origin AS271837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271837 in the RIR database for the space.635 of 636
Route object: none2803:5810:8::/48No route object for it. A route object for 2803:5810::/32 with origin AS271837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271837 in the RIR database for the space.635 of 636
Route object: none2803:5810:e::/48No route object for it. A route object for 2803:5810::/32 with origin AS271837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271837 in the RIR database for the space.635 of 636
Route object: none2803:5810::/48No route object for it. A route object for 2803:5810::/32 with origin AS271837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271837 in the RIR database for the space.634 of 636
Route object: none2803:5810:4::/48No route object for it. A route object for 2803:5810::/32 with origin AS271837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271837 in the RIR database for the space.634 of 636
Route object: none2803:5810:5::/48No route object for it. A route object for 2803:5810::/32 with origin AS271837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271837 in the RIR database for the space.634 of 636
Route object: none2803:5810:6::/48No route object for it. A route object for 2803:5810::/32 with origin AS271837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271837 in the RIR database for the space.634 of 636
Route object: none2803:5810:9::/48No route object for it. A route object for 2803:5810::/32 with origin AS271837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271837 in the RIR database for the space.634 of 636
Route object: none2803:5810:a::/48No route object for it. A route object for 2803:5810::/32 with origin AS271837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271837 in the RIR database for the space.634 of 636
Route object: none2803:5810:b::/48No route object for it. A route object for 2803:5810::/32 with origin AS271837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271837 in the RIR database for the space.634 of 636
Route object: none2803:5810:c::/48No route object for it. A route object for 2803:5810::/32 with origin AS271837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271837 in the RIR database for the space.634 of 636
Route object: none2803:5810:d::/48No route object for it. A route object for 2803:5810::/32 with origin AS271837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271837 in the RIR database for the space.634 of 636
Route object: none2803:5810:f::/48No route object for it. A route object for 2803:5810::/32 with origin AS271837 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271837 in the RIR database for the space.634 of 636
Route object: RIR179.63.20.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR179.63.21.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR179.63.22.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR179.63.23.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
AS-SET: not foundAS-DCNETSAPeeringDB names AS-DCNETSA; no IRR database read has it.

Route objects not announced

Every route object with origin AS271837 is announced.

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.