bgpreport

Network · data from 2026-11-12

AS267549 NetCOMM Fibra

Registry name: AS267549 - NetCOMM FIBRA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267549, 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.
38.156.91.0/24 No ROA Other origin only 668 99% 67
201.182.236.0/22 Valid Other IRR onlyTC 665 99% 67
2804:431c::/32 Valid Other IRR onlyRADB, TC 629 99% 67
201.182.236.0/24 Valid Other IRR onlyTC 205 30% 54
201.182.239.0/24 Valid Other IRR onlyTC 204 30% 54
201.182.238.0/24 Valid Other IRR onlyTC 203 30% 54
201.182.237.0/24 Valid Other IRR onlyTC 202 30% 54

AS-SET

PeeringDB's irr_as_set for AS267549: AS267549:AS-ANNOUNCEMENTS. 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 (AS267549 isn't in the set, or no route object for AS267549 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 objectsAS267549 in itNot covered
AS267549:AS-ANNOUNCEMENTS TC 4214 Yes 1

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

  • ROA: none1
  • Route object: none1
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none38.156.91.0/24No ROA covers it. Add a ROA for AS267549, maxLength 24.668 of 673
Route object: none38.156.91.0/24Route objects for it name AS64134. Add a route object with origin AS267549 in the RIR database for the space.668 of 673
Route object: RIR201.182.236.0/22Route object only in TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:431c::/32Route object only in RADB, TC. Add it in the RIR database for the space.629 of 636
Route object: RIR201.182.236.0/24Route object only in TC. Add it in the RIR database for the space.205 of 673
Route object: RIR201.182.239.0/24Route object only in TC. Add it in the RIR database for the space.204 of 673
Route object: RIR201.182.238.0/24Route object only in TC. Add it in the RIR database for the space.203 of 673
Route object: RIR201.182.237.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673

Route objects not announced

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