bgpreport

Network · data from 2026-11-12

AS267551 DATACOM TELECOM

Registry name: AS267551 - DATACOM TELECOM, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267551, 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:1b00:6000::/41 No ROA None 636 100% 67
2804:1b00:6080::/41 No ROA None 636 100% 67
2804:6344:6000::/41 No ROA None 636 100% 67
2804:6344:6080::/41 No ROA None 636 100% 67
45.70.48.0/22 No ROA Other IRR onlyRADB, TC 670 100% 67
2804:4324::/32 No ROA Other IRR onlyRADB, TC 635 100% 69

AS-SET

AS267551's PeeringDB record names no 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 20 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none2804:1b00:6000::/41No ROA covers it. Add a ROA for AS267551, maxLength 41.636 of 636
Route object: none2804:1b00:6000::/41No route object for it. Add a route object with origin AS267551 in the RIR database for the space.636 of 636
ROA: none2804:1b00:6080::/41No ROA covers it. Add a ROA for AS267551, maxLength 41.636 of 636
Route object: none2804:1b00:6080::/41No route object for it. Add a route object with origin AS267551 in the RIR database for the space.636 of 636
ROA: none2804:6344:6000::/41No ROA covers it. Add a ROA for AS267551, maxLength 41.636 of 636
Route object: none2804:6344:6000::/41No route object for it. Add a route object with origin AS267551 in the RIR database for the space.636 of 636
ROA: none2804:6344:6080::/41No ROA covers it. Add a ROA for AS267551, maxLength 41.636 of 636
Route object: none2804:6344:6080::/41No route object for it. Add a route object with origin AS267551 in the RIR database for the space.636 of 636
ROA: none45.70.48.0/22No ROA covers it. Add a ROA for AS267551, maxLength 22.670 of 673
Route object: RIR45.70.48.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none2804:4324::/32No ROA covers it. Add a ROA for AS267551, maxLength 32.635 of 636
Route object: RIR2804:4324::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

45.70.48.0/23RADBNo ROA
45.70.48.0/24RADBNo ROA
45.70.49.0/24RADBNo ROA
45.70.50.0/23RADBNo ROA
45.70.50.0/24RADBNo ROA
45.70.51.0/24RADBNo ROA
2804:4324::/33RADBNo ROA
2804:4324:8000::/33RADBNo 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.