bgpreport

Network · data from 2026-11-12

AS268311 Dconnect Telecom

Registry name: AS268311 - Dconnect Telecom, BR · PeeringDB

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

Announced routes

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

45.174.180.0/22 Valid Other IRR onlyTC 671 100% 67
45.174.180.0/23 Valid Other IRR onlyTC 671 100% 67
45.174.182.0/23 Valid Other IRR onlyTC 671 100% 67
45.238.40.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
45.238.40.0/23 Valid Other IRR onlyTC 670 100% 67
45.238.42.0/23 Valid Other IRR onlyTC 670 100% 67
45.174.183.0/24 Valid Other IRR onlyTC 666 99% 67
2804:4f34::/32 Valid Other IRR onlyALTDB, RADB, TC 634 100% 67
2804:4f34::/33 Valid Other IRR onlyTC 634 100% 67
2804:4f34:8000::/33 Valid Other IRR onlyTC 634 100% 67
45.174.180.0/24 Valid Other IRR onlyTC 127 19% 44
45.174.181.0/24 Valid Other IRR onlyTC 127 19% 44
45.174.182.0/24 Valid Other IRR onlyTC 126 19% 44
45.238.40.0/24 Valid Other IRR onlyTC 125 19% 44
45.238.41.0/24 Valid Other IRR onlyTC 125 19% 44
45.238.42.0/24 Valid Other IRR onlyTC 125 19% 44
45.238.43.0/24 Valid Other IRR onlyTC 125 19% 44
2804:4f34::/34 Valid Other IRR onlyALTDB, TC 113 18% 43
2804:4f34:4000::/34 Valid Other IRR onlyALTDB, TC 113 18% 43
2804:4f34:8000::/34 Valid Other IRR onlyALTDB, TC 113 18% 43
2804:4f34:c000::/34 Valid Other IRR onlyALTDB, TC 113 18% 43

AS-SET

PeeringDB's irr_as_set for AS268311: AS268311:AS-DCONNECT. 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 (AS268311 isn't in the set, or no route object for AS268311 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 objectsAS268311 in itNot covered
AS268311:AS-DCONNECT ALTDB 6279 Yes 0
TC (also) 92111 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 21 are in fix.csv.

  • Route object: RIR21
ChangePrefix or setDetailFull-table peers
Route object: RIR45.174.180.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.174.180.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.174.182.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.238.40.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.238.40.0/23Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.238.42.0/23Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.174.183.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:4f34::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4f34::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:4f34:8000::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR45.174.180.0/24Route object only in TC. Add it in the RIR database for the space.127 of 673
Route object: RIR45.174.181.0/24Route object only in TC. Add it in the RIR database for the space.127 of 673
Route object: RIR45.174.182.0/24Route object only in TC. Add it in the RIR database for the space.126 of 673
Route object: RIR45.238.40.0/24Route object only in TC. Add it in the RIR database for the space.125 of 673
Route object: RIR45.238.41.0/24Route object only in TC. Add it in the RIR database for the space.125 of 673
Route object: RIR45.238.42.0/24Route object only in TC. Add it in the RIR database for the space.125 of 673
Route object: RIR45.238.43.0/24Route object only in TC. Add it in the RIR database for the space.125 of 673
Route object: RIR2804:4f34::/34Route object only in ALTDB, TC. Add it in the RIR database for the space.113 of 636
Route object: RIR2804:4f34:4000::/34Route object only in ALTDB, TC. Add it in the RIR database for the space.113 of 636
Route object: RIR2804:4f34:8000::/34Route object only in ALTDB, TC. Add it in the RIR database for the space.113 of 636
Route object: RIR2804:4f34:c000::/34Route object only in ALTDB, TC. Add it in the RIR database for the space.113 of 636

Route objects not announced

Every route object with origin AS268311 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.