bgpreport

Network · data from 2026-11-12

AS274723 Cloud Fiber Telecom

Registry name: AS274723 - T. CANASSA TELECOM, BR · PeeringDB

0IPv4 routes
7IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
7No 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 AS274723, seen from no peer

Announced routes

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

2804:92a0::/32 No ROA Other IRR onlyTC 634 100% 67
2804:92a0::/33 No ROA Other IRR onlyTC 634 100% 67
2804:92a0::/34 No ROA Other IRR onlyTC 634 100% 67
2804:92a0:4000::/34 No ROA Other IRR onlyTC 634 100% 67
2804:92a0:8000::/33 No ROA Other IRR onlyTC 634 100% 67
2804:92a0:8000::/34 No ROA Other IRR onlyTC 634 100% 67
2804:92a0:c000::/34 No ROA Other IRR onlyTC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS274723: AS-274723. 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 (AS274723 isn't in the set, or no route object for AS274723 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 objectsAS274723 in itNot covered
AS-274723 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 15 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none2804:92a0::/32No ROA covers it. Add a ROA for AS274723, maxLength 32.634 of 636
Route object: RIR2804:92a0::/32Route object only in TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:92a0::/33No ROA covers it. Add a ROA for AS274723, maxLength 33.634 of 636
Route object: RIR2804:92a0::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:92a0::/34No ROA covers it. Add a ROA for AS274723, maxLength 34.634 of 636
Route object: RIR2804:92a0::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:92a0:4000::/34No ROA covers it. Add a ROA for AS274723, maxLength 34.634 of 636
Route object: RIR2804:92a0:4000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:92a0:8000::/33No ROA covers it. Add a ROA for AS274723, maxLength 33.634 of 636
Route object: RIR2804:92a0:8000::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:92a0:8000::/34No ROA covers it. Add a ROA for AS274723, maxLength 34.634 of 636
Route object: RIR2804:92a0:8000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:92a0:c000::/34No ROA covers it. Add a ROA for AS274723, maxLength 34.634 of 636
Route object: RIR2804:92a0:c000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
AS-SET: not foundAS-274723PeeringDB names AS-274723; no IRR database read has it.

Route objects not announced

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